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
361 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
Instead of "latest" or no version tag, I think you'd just need to put the desired version in your compose file.
In this case it sounds like you want to upgrade to 10.10.7 first, so you'd use that for your tag. Based on the tag I found here: https://hub.docker.com/layers/jellyfin/jellyfin/10.10.7/images/sha256-3b38dae4c3ddd6ebc7378538fba4d3f314070ebefbdb3d688166b7c8658fb123
After updating your compose stack to that version and confirming a successful upgrade in jellyfin, then you could remove the version tag (to pull latest by default).