this post was submitted on 25 Aug 2023
33 points (97.1% liked)

Selfhosted

60451 readers
871 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.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Hello,

I moved my home servers to fedora silverblue and docker-compose (ipv6 reasons :/). I stumpled upon the problem that I neither wanted to update image tags manually, nor have no idea what ":latest" deployed on my server in case I need to roll back.

To alleviate that problem, I made a small update-tool. It takes care of writing down the image@sha256... digest every time so that you can roll back. It also automatically snapshots and restarts the services.

It is made in Python but doesn't need any dependencies, so no catering for a venv either. You only need to have skopeo and snapper in working order. Maybe you'll find it useful, but please be aware that it is in an early stage. Also I'm not responsible if it nukes your server ๐Ÿ˜…

top 1 comments
sorted by: hot top controversial new old
[โ€“] kolorafa@lemmy.world 1 points 2 years ago

I like the concept, you could also detect the compose file name automatically.

Or write down hashes for tag even if compose don't use your variables so reading from compose, so people would not need to relay on the script but could use it as additional backup