2024-08-16, 02:48 AM
(This post was last modified: 2024-08-16, 02:49 AM by Efficient_Good_5784.)
First, stop worrying about the cache folder. That doesn't matter if it's lost.
Second, I see what you did.
For the config folder, there's a 2nd config folder inside of it. You have /volume1/docker/jellyfin mapped to /config/config.
As in, you only exposed the sub-level config folder and not the top-level one.
The top-level config folder contains all configurations for the server.
What you should have done at the start is this: /volume1/docker/jellyfin : /config:rw
The image would just populate the entire config folder there.
I would add a new volume mount to a blank space on your NAS, then go to the Container Manager. There, open the old Jellyfin image, and open a terminal.
In the terminal page, create a new bash session into the Docker container and copy the config folder to the blank volume you just set up.
Once the copy is complete, you can use the file browser to move that config folder wherever you need it. Just make sure to make a backup of it for the new version.
Second, I see what you did.
For the config folder, there's a 2nd config folder inside of it. You have /volume1/docker/jellyfin mapped to /config/config.
As in, you only exposed the sub-level config folder and not the top-level one.
The top-level config folder contains all configurations for the server.
What you should have done at the start is this: /volume1/docker/jellyfin : /config:rw
The image would just populate the entire config folder there.
I would add a new volume mount to a blank space on your NAS, then go to the Container Manager. There, open the old Jellyfin image, and open a terminal.
In the terminal page, create a new bash session into the Docker container and copy the config folder to the blank volume you just set up.
Once the copy is complete, you can use the file browser to move that config folder wherever you need it. Just make sure to make a backup of it for the new version.