After I login to my Pi-Hole v6 dashboard, I see the following in the footer:
Docker Tag development
Core vDev (development, 1bec0d2c)· Update available!
FTL vDev (development, 8504bb9b) · Update available!
Web interface vDev (development, cd916b17) · Update available!
In the past with this v6 Docker, I would ssh in and then run the following commands to update the components:
$ doas docker-compose down
$ doas docker-compose pull
$ doas docker-compose up -d
Now when I follow the same process which I've been doing since I've been testing Pi-Hole v6 for many months at this point, it stops updating the components. How do I get it to update like it has in the past?
services:
pihole:
container_name: pihole
image: pihole/pihole:development
ports:
# DNS Ports
- "53:53/tcp"
- "53:53/udp"
# Default HTTP Port
- "80:80/tcp"
# Default HTTPs Port. FTL will generate a self-signed certificate
- "443:443/tcp"
environment:
# Set the appropriate timezone for your location (https://en.wikipedia.org/wiki/List_of_tz_database_time_zones), e.g:
TZ: 'America/New_York'
# Set a password to access the web interface. Not setting one will result in a random password being assigned
FTLCONF_webserver_api_password: '<<OMITTED>>'
# Volumes store your data between container upgrades
volumes:
# For persisting Pi-hole's databases and common configuration file
- './etc-pihole:/etc/pihole'
restart: unless-stopped
When I look at the Docker tags here, https://hub.docker.com/r/pihole/pihole/tags, I see both development and latest. Is latest then the "newest" version 5.x of Pi-Hole and then development is the "newest" version 6.x of Pi-Hole? Is nightly tag the bleeding edge of 6.x Pi-Hole development?
latest image will always point to the most recent "Date-based" image. These images contain the most recent versions of master branches (core, web and FTL).
nightly image will always contain the most recent versions in development branches (core, web and FTL) - This is the image you want, but be careful... this is where things break.
development image was created to test the development branch of docker-pi-hole repository itself.
In the past, development image contained the same branches as latest (but docker dev).
Now we are in a transition period (master is v5 and development is v6).
We decided to use the v6 development branches here to simplify testing.
Why are you seeing the update notifications if you never saw that before?
Until 2 weeks ago, the docker repository was in constant change because we were merging a lot of pull requests in docker repository, so every day a new image was created using the most recent core, web and FTL branches.
Now the "merge speed" in docker repo decreased because there are few PRs waiting, but other repositories are still constantly changing. The result is: development image is currently 2 weeks old, using core, web and FTL branches from 2 weeks ago.
.