Hi,
your configuration is missing the mounts for the config dir and cache dir. In the section "Volume" you need to add the following lines:
With these additional mounts, Docker will persist everything Jellyfin is writing in /config and /cache and you can access the files there via Synology File Manager and other tools, back them up (eg. by copying them while Jellyfin isn't running) and restart/recreate/upgrade the Jellyfin container without losing them.
You may have to create the folders /volume1/docker/jellyfin/config and /volume1/docker/jellyfin/cache before updating the container configuration in Container Manager and it will lead to losing the metadata and other information stored in Jellyfin once again because Jellyfin will start over with these new (initially empty) folders. But then you won't lose them again.
Every time you want to upgrade Jellyfin, you should stop the container and make a copy of the folder /volume1/docker/jellyfin/config before upgrading so you can revert everything if something goes wrong during or after the upgrade.
You may also want to change the docker image tag from "latest" to "10.11.0" so that you can better control which version of docker you are using and prevent Synology from upgrading Jellyfin automatically.
I personally prefer to use Docker Compose to do the configuration because it's easier to maintain. You need a bit of knowledge about Docker (Compose) for that, but you can do so in Synology Container Manager by creating a "Project" and providing a YAML configuration for it (which is a regular Docker Compose configuration file).
your configuration is missing the mounts for the config dir and cache dir. In the section "Volume" you need to add the following lines:
Code:
/volume1/docker/jellyfin/config:/config
/volume1/docker/jellyfin/cache:/cacheWith these additional mounts, Docker will persist everything Jellyfin is writing in /config and /cache and you can access the files there via Synology File Manager and other tools, back them up (eg. by copying them while Jellyfin isn't running) and restart/recreate/upgrade the Jellyfin container without losing them.
You may have to create the folders /volume1/docker/jellyfin/config and /volume1/docker/jellyfin/cache before updating the container configuration in Container Manager and it will lead to losing the metadata and other information stored in Jellyfin once again because Jellyfin will start over with these new (initially empty) folders. But then you won't lose them again.
Every time you want to upgrade Jellyfin, you should stop the container and make a copy of the folder /volume1/docker/jellyfin/config before upgrading so you can revert everything if something goes wrong during or after the upgrade.
You may also want to change the docker image tag from "latest" to "10.11.0" so that you can better control which version of docker you are using and prevent Synology from upgrading Jellyfin automatically.
I personally prefer to use Docker Compose to do the configuration because it's easier to maintain. You need a bit of knowledge about Docker (Compose) for that, but you can do so in Synology Container Manager by creating a "Project" and providing a YAML configuration for it (which is a regular Docker Compose configuration file).