Updating an image does not update the container.

[Magicrafter13]

Cockpit version: 320
Cockpit-podman version: 90
Podman version: 5.1.1
OS: Fedora Server 40

When I update a tagged image, the container somehow continues using its old version of the image. And if I delete that "intermediate" image the container is deleted as well.

Steps to reproduce

1. Create a container with [some_image]:latest
2. Wait for a new release of the image with the same 'latest' tag
3. Stop the container (from web UI or CLI)
4. Run podman pull [some_image]:latest to update
5. Start the container again (once again, web UI or CLI)
6. Observe that the container is not using the latest image after all (you may want to use a container which logs its version number or something)

Here we see the intermediate image which tells us it is being used by Pi-Hole.

Here we see that Pi-Hole claims to be using docker.io/pihole/pihole:latest.

And finally we see that the actual image of docker.io/pihole/pihole:latest is not in fact being used by any containers.

[jelly]

Pulling an image does not automatically update the running container(s), this is by design you don't want pulling an image to influence running containers.

You can however setup podman to automatically update a running container but that requires using a systemd unit or quadlet https://docs.podman.io/en/latest/markdown/podman-auto-update.1.html

[Magicrafter13]

Perhaps I should have this changed to a feature request then? Until then I've begun moving my containers over to systemd podman. Pi-Hole is giving me trouble but I got my more important ones up and running and everything seems to work fine. Took a lot of fiddling though...

I'll check back every so often to see if the updates work - I think I've configured the unit files correctly for the automatic image pulls.