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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
Be aware you need to enable and start
podman-auto-update.timerfor this to work automatically (iesystemctl 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.timerfor each user.thanks for the addition!
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.
How do you circumvent it?
You kindly ask the maintainer of the container repository to add major version tags ;)
👍🏻
thanks for the addition :)