this post was submitted on 12 Apr 2026
103 points (96.4% liked)

Selfhosted

60482 readers
508 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.

  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.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Back in the day it was nice, apt get update && apt get upgrade and you were done.

But today every tool/service has it's own way to being installed and updated:

  • docker:latest
  • docker:v1.2.3
  • custom script
  • git checkout v1.2.3
  • same but with custom migration commands afterwards
  • custom commands change from release to release
  • expect to do update as a specific user
  • update nginx config
  • update own default config and service has dependencies on the config changes
  • expect new versions of tools
  • etc.

I selfhost around 20 services like PieFed, Mastodon, PeerTube, Paperless-ngx, Immich, open-webui, Grafana, etc. And all of them have some dependencies which need to be updated too.

And nowadays you can't really keep running on an older version especially when it's internet facing.

So anyway, what are your strategies how to keep sanity while keeping all your self hosted services up to date?

you are viewing a single comment's thread
view the rest of the comments
[–] Overspark@piefed.social 10 points 2 months ago (1 children)

Podman automatically updates my containers for me.

[–] jeena@piefed.jeena.net 5 points 2 months ago* (last edited 2 months ago) (1 children)

Because you point to :latest and everything is dockerized and on one machine? How does it know when it's time to upgrade?

[–] Overspark@piefed.social 5 points 2 months ago (1 children)

Yeah only for :latest containers, that's true. It automatically runs a daily service to check whether there are newer images available. You can turn it off per container if you don't want it.

One of the nice things about it is that I have containers running under several different users (for security reasons) so that saves me a lot of effort switching to all these users all the time.

[–] melroy@kbin.melroy.org -1 points 2 months ago (2 children)

It's a bad practice to use latest tag

[–] prenatal_confusion@feddit.org 9 points 2 months ago* (last edited 2 months ago)

Depends on what you want to do. For production with sensitive data, yes it is. For my ytdl and jellyfin? Perfectly fine.

[–] Overspark@piefed.social 6 points 2 months ago

Depends. There are a few things I update by hand, but as long as you have proper backups it's generally safer to run the latest versions of things automatically if you don't mind the possibility of breakage (which is very rare in my experience). This is in the context of self-hosting of course, not a business environment.