I did not use the addon portainer and I do not know the details or the requirements. However I can suggest you install the portainer container with this SSH command:
docker run --name=9000-portainer \
--restart unless-stopped \
-v /var/run/docker.sock:/var/run/docker.sock \
-v /storage/.config/dockers/portainer/data:/data \
-p 9000:9000 \
-d portainer/portainer-ceand the updater watchtower container with this SSH command:
docker run -d \
--name watchtower-updater \
-v /var/run/docker.sock:/var/run/docker.sock \
containrrr/watchtower --run-onceThe watchtocher container is configured to run manually (is always stopped) and only once, and of course it never deletes any docker images. I have been using this for a long time without any problem.
Obviously you must delete the portainer and updater addons so that there are no conflicts with this alternative.
Updater only automatically deletes orphaned images, such as the ones that lost their tag because a newer image was downloaded for that tag. It doesn't auto delete non orphaned images even if they are not attached to a container.
The prune button in the addon settings however does remove all images not attached to a container, but that is a manual operation, not automated.
In other words, updater's cron operation uses "docker image prune -f" whereas the manual button uses "docker image prune -af" with the "a" being the critical flag.
Automatic image update for docker containers is a very bad idea:
Automatic image update for docker containers is a very bad idea:
- there are containers that may have incompatibilities with others and whose update must be executed in a certain order, and even stop some while updating another (example: my wireguard server must start after pihole)
- updating a docker image can lead to an interruption of the streaming service (vpn, tv, video, ...)
- updating a docker image always creates a risky situation that should not be left to an automatic timer
It doesn't auto recreate containers. It only updates the image so none of those concerns are applicable here.
I just realized the mention of watchtower above. So I should clarify my previous post. The updater addon that is referenced in the thread title doesn't auto recreate containers. So it's fine.
Watchtower however is often used to auto recreate containers based on image updates and that is indeed a bad idea. Never recreate containers when not paying attention.
Updater only automatically deletes orphaned images, such as the ones that lost their tag because a newer image was downloaded for that tag. It doesn't auto delete non orphaned images even if they are not attached to a container.
https://github.com/linuxserver/li…ver.updater#L22
The prune button in the addon settings however does remove all images not attached to a container, but that is a manual operation, not automated.
https://github.com/linuxserver/li…settings.xml#L6
In other words, updater's cron operation uses "docker image prune -f" whereas the manual button uses "docker image prune -af" with the "a" being the critical flag.
It's interesting to know what the scripts actually do. Thanks. I thought the update did something else, like download the images, but I see it's empty.
In case it helps anyone, to avoid using watchtower with more containers and take advantage of existing scripts I have used this script which simply downloads the new images for the containers in use. So when updating, whether from Portainer or elsewhere, you can clearly see the containers with outdated images and it deploys much faster.
This is compatible with the prune script, as it doesn't delete tagged images. Only the orphaned ones that will be generated when actually deploying containers with the new image.
#!/bin/sh
# To add to cron copy this file in /storage/.kodi/userdata/addon_data/docker.linuxserver.updater/update.sh
# chmod +x /storage/.kodi/userdata/addon_data/docker.linuxserver.updater/update.sh
# Get the list of active containers
containers=$(docker ps --format "{{.Names}}")
for container in $containers; do
# Get the image used by the container
image=$(docker inspect --format '{{.Config.Image}}' "$container")
echo "Pulling latest image for container: $container (Image: $image)"
docker pull "$image"
done
