2025-02-25, 12:07 AM
(This post was last modified: 2025-02-25, 12:14 AM by Efficient_Good_5784. Edited 2 times in total.)
When dealing with Docker containers, you don't update the current one.
Updating involves creating a new container and deleting the old one.
Since Docker containers are self-contained (hence the name "container"), you lose everything inside the container when you delete it.
This is where external host mounts come into play.
Updating Jellyfin on Docker is not hard. All you need is to carry over the old /config data and use it for the new container.
Looking at the guide you followed, I'm assuming you never created a host mount for /config, which means that all your config data is inside the container.
What you're going to need to do is:
1. On your NAS, create a blank folder
2. Stop the Jellyfin container
3. Add the blank folder you created as an external mount to the container
4. Run the container, then on Container Manager open the container's terminal and create a bash instance
5. In the bash instance, use Linux commands to copy the /config directory to the blank folder
After that's done, you now have the config folder accessible on the outside.
Just copy that to wherever you want to host it for your current or future containers.
Then to actually update, you just get the new latest image of Jellyfin and run that while linking your old config folder.
I would advise you to make a backup before doing so in case you don't like the update or something goes wrong.
Also make sure to copy the config folder while no one is using your server or tasks are running to avoid possibly copying the database while it's in use.
If the copy is made of the database while it was in use, you risk the copy being corrupted.
You can also read my guide here for installing Jellyfin on DSM7 and see if it helps you: https://forum.jellyfin.org/t-guide-runni...er-compose
Updating involves creating a new container and deleting the old one.
Since Docker containers are self-contained (hence the name "container"), you lose everything inside the container when you delete it.
This is where external host mounts come into play.
Updating Jellyfin on Docker is not hard. All you need is to carry over the old /config data and use it for the new container.
Looking at the guide you followed, I'm assuming you never created a host mount for /config, which means that all your config data is inside the container.
What you're going to need to do is:
1. On your NAS, create a blank folder
2. Stop the Jellyfin container
3. Add the blank folder you created as an external mount to the container
4. Run the container, then on Container Manager open the container's terminal and create a bash instance
5. In the bash instance, use Linux commands to copy the /config directory to the blank folder
After that's done, you now have the config folder accessible on the outside.
Just copy that to wherever you want to host it for your current or future containers.
Then to actually update, you just get the new latest image of Jellyfin and run that while linking your old config folder.
I would advise you to make a backup before doing so in case you don't like the update or something goes wrong.
Also make sure to copy the config folder while no one is using your server or tasks are running to avoid possibly copying the database while it's in use.
If the copy is made of the database while it was in use, you risk the copy being corrupted.
You can also read my guide here for installing Jellyfin on DSM7 and see if it helps you: https://forum.jellyfin.org/t-guide-runni...er-compose
