this post was submitted on 09 Mar 2024
39 points (97.6% liked)

Selfhosted

40152 readers
512 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 1 year ago
MODERATORS
 

My main resource is the podman documentation

There is a podman-auto-update.service systemd service. It was not enabled on my fedora atomic GNOME installation.

You can start it with systemctl start podman-auto-update.service It'll auto update daily at 00:00.

For a container to auto update, you have to add

    labels:
      - "io.containers.autoupdate=registry"

to the compose.yml file, otherwise it won't be updated. (only auto update if you specify it)

Make sure that the image is specified correctly with the source, e.g. ghcr.io/advplyr/audiobookshelf or docker.io/jellyfin/jellyfin.

You can then run podman auto-update --dry-run and if you are satisifed with it, test the first auto update with podman auto-update.

top 7 comments
sorted by: hot top controversial new old
[–] samwwwblack@lemm.ee 4 points 8 months ago (1 children)

You can start it with systemctl start podman-auto-update.service It’ll auto update daily at 00:00.

Be aware you need to enable and start podman-auto-update.timer for this to work automatically (ie systemctl enable --now podman-auto-update.timer), this command will just update the images once only.

I don't think this works for non-system podman images, so you'd have to do systemctl --user enable --now podman-auto-update.timer for each user.

[–] barbara@lemmy.ml 1 points 8 months ago

thanks for the addition!

[–] poVoq@slrpnk.net 2 points 8 months ago (2 children)

Yeah, works great in my experience, but requires a bit of care if the upstream container packager is only doing a "latest" tag and not major version tags that are unlikely to break compatibility.

[–] barbara@lemmy.ml 1 points 8 months ago (1 children)
[–] poVoq@slrpnk.net 2 points 8 months ago (1 children)

You kindly ask the maintainer of the container repository to add major version tags ;)

[–] barbara@lemmy.ml 1 points 8 months ago
[–] barbara@lemmy.ml 1 points 8 months ago* (last edited 8 months ago)

thanks for the addition :)