57
Docker question: updating container to specific version
(discuss.tchncs.de)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 21 Oct 2025
57 points (100.0% liked)
Selfhosted
52583 readers
385 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:
-
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).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
It's always good practice to back up your data before doing an upgrade. But in case you need it, you can certainly do a minor version update through compose. If you already have that set up, it'll probably be the easier route.
Your compose file should have a line that looks like this:
possibly with a version number. You can specify which version you want by changing that line. For example:
You can check which versions are available here.
This looks simple enough, thanks for taking the time to write that out for me!
don't forget to recreate the container after editing the file, or else you'll keep running your previous Jellyfin version. "docker compose start" does not do it, "docker compose up" does when it detects a change.
Good point, thanks!
Its also good practice to include the sha256 digest after the version like
If you pull without digest and say the maintainers get compromised and release an update with the same version tag with malicious stuff in it, then you won't pull it automatically since the digest does not match.
You can only do that if you get a specific version, or can this be done in some way with just leaving it to latest version?
I believe you can just do the sha but it would be a similar affect pinning it to that sxact docker image, but doing so without version tag makes it harder for you to know what you are running.
The sha256 is generated by an algorithm based off of the bytes of the image wherr the tag is overwritable and pushed by the developer.