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

Selfhosted

60970 readers
571 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
111
How do you keep docker/podman containers up-to-date? (lemmy.world)
submitted 3 years ago by cat@lemmy.world to c/selfhosted@lemmy.world
66 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
[–] roofuskit@kbin.social 1 points 3 years 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.

[–] psykal@lemmy.fmhy.ml 0 points 3 years ago* (last edited 3 years 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.

[–] roofuskit@kbin.social 1 points 3 years ago (1 children)

What is driving you to need to update so often?

[–] psykal@lemmy.fmhy.ml 1 points 3 years ago (1 children)

Nothing. Is this too frequent?

[–] roofuskit@kbin.social 1 points 3 years 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.