Selfhosted

60951 readers

586 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Docker question: updating container to specific version (discuss.tchncs.de)

submitted 9 months 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?

you are viewing a single comment's thread
view the rest of the comments

[–] cheesemoo@lemmy.world 13 points 9 months ago* (last edited 9 months 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).