I have watchtower to keep my 50 production docker containers up to date. So far I have never had to resort to an old image since the new one was bugged but I know of the risks and dont have the --cleanup flag activated so I could easily spin up the old image if necessary. I also keep daily (mirrored) backups so I should be ok in the case of failure.
But I keep running into space issues due to multiple GBs of old images that I have to manually remove to not fill up the rather small ssd.
Does anyone have an idea how to automatically remove all but the newest unused docker image so I can quickly revert to it in case of failure but once there is another unused one of this container it goes away?
It’s probably no big deal but searching for it together with watchtower didnt yield anything so far.
Not to sound flippant, but it seems like a solution looking for a problem. I use the --cleanup flag, and if there’s an issue, rolling back is as simple as changing dockerimage:latest to dockerimage:version that worked.
Pretty much this. I don’t even bother with watchtower anymore. I just run this script from cron pointed at the directory I keep my directories of active docker containers and their compose files:
#/bin/sh
for d in /home/USERNAME/stacks/*/
do
(cd “$d” && docker compose pull && docker compose up -d --force-recreate)
done;
for e in /home/USERNAME/dockge/
do
(cd “$e” && docker compose pull && docker compose up -d --force-recreate)
done;
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Not to sound flippant, but it seems like a solution looking for a problem. I use the --cleanup flag, and if there’s an issue, rolling back is as simple as changing dockerimage:latest to dockerimage:version that worked.
Unless I’m missing something.
Pretty much this. I don’t even bother with watchtower anymore. I just run this script from cron pointed at the directory I keep my directories of active docker containers and their compose files:
#/bin/sh for d in /home/USERNAME/stacks/*/ do (cd “$d” && docker compose pull && docker compose up -d --force-recreate) done; for e in /home/USERNAME/dockge/ do (cd “$e” && docker compose pull && docker compose up -d --force-recreate) done;
docker image prune -a -f
I agree. If OP is scared that the image creator is clearing the old images, then OP should just mirror the registry or just have a system backup.