57
Docker question: updating container to specific version (discuss.tchncs.de)
submitted 1 week ago by ook@discuss.tchncs.de to c/selfhosted@lemmy.world
8 comments fedilink hide all child comments

This is related to the recent massive Jellyfin upgrade. The Jellyfin team recommends to only upgrade directly to the new version from version 10.10.7.

I checked my server and I happened to be a bit slow, I got 10.10.3. Maybe that is fine but I don't want to take any chances. Then I realised I have no idea how I'd get this specific version first before upgrading to the latest version, with using docker.

I tried finding the answer but somehow couldn't really find a good page explaining it. Can I do this with docker compose or maybe it is better to just run this one time without compose? How to do it and what is easier?

top 8 comments
sorted by: hot top controversial new old
[-] cx40@piefed.ca 38 points 1 week ago

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:

image: jellyfin/jellyfin

possibly with a version number. You can specify which version you want by changing that line. For example:

image: jellyfin/jellyfin:10.10.7

You can check which versions are available here.

[-] ook@discuss.tchncs.de 10 points 1 week ago

This looks simple enough, thanks for taking the time to write that out for me!

[-] seang96@spgrn.com 6 points 6 days ago

Its also good practice to include the sha256 digest after the version like

DockerImage:v... @sha256:...

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.

[-] ook@discuss.tchncs.de 1 points 6 days ago

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?

[-] seang96@spgrn.com 1 points 6 days ago

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.

[-] WhyJiffie@sh.itjust.works 3 points 6 days ago

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.

[-] ook@discuss.tchncs.de 1 points 6 days ago

Good point, thanks!

[-] cheesemoo@lemmy.world 12 points 1 week ago* (last edited 1 week ago)

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).

this post was submitted on 21 Oct 2025
57 points (100.0% liked)

Selfhosted

52583 readers
648 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 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz