this post was submitted on 07 Jul 2023
111 points (99.1% liked)

Selfhosted

40733 readers
400 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
111
How do you keep docker/podman containers up-to-date? (self.selfhosted)
submitted 1 year ago by cat to c/selfhosted
61 comments fedilink hide all child comments
 

I used to simply use the 'latest' version tag, but that occasionally caused problems with breaking changes in major updates.

I'm currently using podman-compose and I manually update the release tags periodically, but the number of containers keeps increasing, so I'm not very happy with this solution. I do have a simple script which queries the Docker Hub API for tags, which makes it slightly easier to find out whether there are updates.

I imagine a solution with a nice UI for seeing if updates are available and possibly applying them to the relevant compose files. Does anything like this exist or is there a better solution?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago (1 children)

It depends on the project. If the project doesn't make an effort to highlight them I would consider using a different one.

But any decent OSS will make a good change log for their updates that you can read.

[–] [email protected] 0 points 1 year ago* (last edited 1 year ago) (1 children)

I've just been updating my containers every week or so and if something breaks I'll try and fix it. It would definitely be preferable to "fix" in advance, but with enough containers getting updated, checking/reading every change becomes a fair amount of work. Most of the time nothing breaks.

Downvotes are cool but if this is a bad way of doing things just tell me.

[–] [email protected] 1 points 1 year ago (1 children)

What is driving you to need to update so often?

[–] [email protected] 1 points 1 year ago (1 children)

Nothing. Is this too frequent?

[–] [email protected] 1 points 1 year ago

Well, there's always the "if it ain't broke don't fix it" mantra. There's a few reasons I tend to update. Because there's a feature I want or need, to fix a big that affects me, or because a software frequently updates with breaking changes and keeping up with reading change logs is the best way to deal with that. The last option is usually because if I keep up with it I don't have to read and fix multiple months of breaking changes.