+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: General Questions (https://forum.jellyfin.org/f-general-questions)
+--- Thread: How do i save metadata outside my docker? (/t-how-do-i-save-metadata-outside-my-docker)
How do i save metadata outside my docker? - Cycron - 2025-04-14
Hello everyone,
first of all, thank you very much for your help here in the forum. I hope I've come to the right place with my question.
Unfortunately I have a problem and almost no idea about Docker... and I am convinced that this is exactly the issue.
Whenever I want to update the latest version of Jellyfin, I have to update the image on my NAS. So far so good. However, if Iam right, I have to close the running container and boot the newer image in a new container. That wouldn't be a problem, if I didn't also have to re-scrape the metadata. The images (Cover etc.) for the media are placed in the same folders as media itself, but the collections, actors and description of the media etc. were stored in the old container and I have to reorganize everything after an update.
Is it possible to redirect the metadata within the Docker container to my NAS and retrieve it from there after the update?
I use a Synology NAS and I have the possibility to access the docker container via console. I'm not asking for 1:1 instructions, but I'm searching my ass off on the internet for reasonable information explaining how to tell the container to export the metadata and then specify it as the source for the new container.
Or am I just a DAU and too stupid to update my container without losing the data inside the running one?
I would be so damn grateful if you could at least give me a nudge in the right direction.
RE: How do i save metadata outside my docker? - TheDreadPirate - 2025-04-14
You should be specifying a path on your host to mount /config. If you are NOT doing that, the storage for /config would exist in the virtual file system that each container creates for itself. When you update to a new version of any app, it would create a new virtual file system as it is considered a whole new container.
It SOUNDS like you are NOT specifying a host path for /config and /cache.