Selfhosted

40198 readers

690 users here now

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
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Script (for watchtower?) removing all but the last old docker image (lemmy.giftedmc.com)

submitted 10 months ago by [email protected] to c/[email protected]

11 comments fedilink hide all child comments

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.

Thanks in advance and have a good one.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 10 months ago (1 children)

Yeah, I found the docker system prune filter option in the docs as well. Very unprecise sadly but thanks for mentioning it. :) I'm thinking of something like "when updating, first copy the version number of the old image and exclude it from prune". Probably going to have to write something myself again. Feel free to spitball with me.

[–] [email protected] 1 points 9 months ago (1 children)

So my thought with the time based pruning is that you can keep a backup that's X days old.

Let's say you keep 2 weeks. If there have been no problems with an image after 2 weeks of an update, you're probably good to go. If you have an issue during those 2 weeks, you can return to and image within those 2 weeks. If you've had no problems after 2 weeks, it's probably stable.

Adjust 2 weeks to whatever you're comfortable with.

[–] [email protected] 1 points 9 months ago (1 children)

This would absolutely make sense, were it not for the fact that the old image can be 3 weeks old when the new one comes out. Feel free to correct me but I think a time based option on age is not sufficient.

[–] [email protected] 2 points 9 months ago (1 children)

Correct, that would not work for that case.

[–] [email protected] 1 points 9 months ago

But thanks for suggesting and spitballing with me.