# Update does not happen on Docker Container re-deployment

**URL:** <https://discourse.pi-hole.net/t/update-does-not-happen-on-docker-container-re-deployment/86500>\
**Category:** Help\
**Created:** [June 20, 2026, 8:40pm UTC](https://discourse.pi-hole.net/t/update-does-not-happen-on-docker-container-re-deployment/86500 "2026-06-20T20:40:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![WormArt075](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/w/47e85d/32.png) [@WormArt075](https://discourse.pi-hole.net/u/WormArt075)\
**Post date:** [June 20, 2026, 8:40pm UTC](https://discourse.pi-hole.net/t/update-does-not-happen-on-docker-container-re-deployment/86500/1 "2026-06-20T20:40:14Z")

</div>

## 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:

- 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/](https://tricorder.pi-hole.net/NJ6Ofa5n/)

---

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [June 20, 2026, 8:45pm UTC](https://discourse.pi-hole.net/t/update-does-not-happen-on-docker-container-re-deployment/86500/2 "2026-06-20T20:45:34Z")

</div>

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](https://docs.pi-hole.net/docker/upgrading/), e.g.

```auto
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.

---

<div class="post-metadata">

**Author:** ![rdwebdesign](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/rdwebdesign/32/51363_2.png) [@rdwebdesign](https://discourse.pi-hole.net/u/rdwebdesign)\
**Post date:** [June 20, 2026, 8:52pm UTC](https://discourse.pi-hole.net/t/update-does-not-happen-on-docker-container-re-deployment/86500/3 "2026-06-20T20:52:27Z")

</div>

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:

1. stop the stack
2. go to the "Images" menu and delete the old `pihole/pihole:latest` image
3. restart the stack.

---

<div class="post-metadata">

**Author:** ![WormArt075](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/w/47e85d/32.png) [@WormArt075](https://discourse.pi-hole.net/u/WormArt075)\
**Post date:** [June 21, 2026, 7:13am UTC](https://discourse.pi-hole.net/t/update-does-not-happen-on-docker-container-re-deployment/86500/7 "2026-06-21T07:13:58Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [July 12, 2026, 7:14am UTC](https://discourse.pi-hole.net/t/update-does-not-happen-on-docker-container-re-deployment/86500/8 "2026-07-12T07:14:03Z")

</div>

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.