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.
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.
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.
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/...
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).
thanks for using Leebra!
go to feed...
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.
save