cx40 43 points a year 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.

save

path: 0 20053490, hotness: undefined, score: 43, children: 6

ook 13 points a year ago

save

path: 0 20053490 20054446, hotness: undefined, score: 13, children: 5

seang96 6 points a year 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.

save

path: 0 20053490 20054446 20058937, hotness: undefined, score: 6, children: 2

WhyJiffie 3 points a year 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.

save

path: 0 20053490 20054446 20071707, hotness: undefined, score: 3, children: 1