Expected Behaviour:
On the bottom of the admin page "update available" is blinking red and below the suggestion "to install updates, replace this old container with a fresh updated image". Via Portainer-CE I re-deploy the Container by forcing it to pull it again from pihole/pihole:latest but it won't update.
-
Debian Linux Trixie
-
HP EliteDesk i5-8500T 16GB RAM
-
Docker compose file:
pihole:
container_name: pihole
image: pihole/pihole:latest
restart: unless-stopped
network_mode: host
depends_on:
unbound:
condition: service_healthy
environment:
TZ: "Europe/Zurich"
FTLCONF_webserver_api_password: "${PIHOLE_PASSWORD}"
FTLCONF_dns_upstreams: "172.31.0.3#5335;172.31.0.3#5335"
FTLCONF_dns_dnssec: "true"
FTLCONF_dns_bogusPriv: "true"
FTLCONF_dns_listeningMode: "all"
FTLCONF_webserver_port: "8080"
FTLCONF_ntp_ipv4_active: "false"
FTLCONF_ntp_ipv6_active: "false"
volumes:
- /opt/pihole/etc-pihole:/etc/pihole
- /mnt/nas/docker/pihole/etc-dnsmasq.d:/etc/dnsmasq.d
cap_add:
- NET_ADMIN
-
Docker engine version 29.6.0
Actual Behaviour:
The Container is not being updated (from the actual 2026.05.0 to the new 2026.06.0)
Debug Token:
https://tricorder.pi-hole.net/NJ6Ofa5n/
You are pulling an image, not a container.
Redeploying a container will reuse the already deployed container, which in your case was created from a previous image.
You need to replace the existing container based on 2026.05.0 and deploy a new one based on 2026.06.00.
The necessary steps for plain Docker or docker-compose are described in Docker ยป Upgrading, e.g.
docker pull pihole/pihole:latest
docker stop pihole
docker rm pihole
docker run [ ... your arguments here ... ]
You need to perform the equivalent actions with Portainer.
This is not a Pi-hole issue.
For some reason, Portainer won't download the new image automatically if you simply stop and restart the stack.
While writing this reply, I just updated one of my instances (which I had forgotten to update last week), using Portainer and it only updates the image if you execute these steps:
- stop the stack
- go to the "Images" menu and delete the old
pihole/pihole:latest image
- restart the stack.
Somehow this worked today but did not work a couple of days ago - and I did exactly the same: in Portainer CE I simply re-deployed it by forcing the download of the image.
Anyway: THANKS