When I first set up my jf docker image I left the config and data directories in the docker contain I stead of poi t them out side.
Now when I try to update I lose ally meta data. Is there a way to move those folders before I upgrade?
You’re just running in docker, so you’d want to make sure you map a local folder into your container (at a different location than they are already!), then get into the container and copy your files to the host’s mapped folder. Once that’s complete, update your docker to point your local folder to the proper config location and it should keep everything local after you upgrade.
Edit: In my compose, I have this line
/jellyfin/jellyfin-data:/config
so you could map it to :/backup on your first boot, copy /config to /backup, then update your compose to map it to /config and you’re good to go!
Glad to hear it. I’ll be honest, I wasn’t aware of that command, I’ve just always done it the hard way and logged into the console of the container. I have this line in my .bashrc on all my docker hosts:
alias docker-console='docker exec -it "${PWD##*/}" bash'
I feel like there is a way to copy stuff from docker-volumes to disk and then point docker to the folders on the disk as external volumes, I think I’ve done that at some point years back, but not sure how to do it exactly.
When I first set up my jf docker image I left the config and data directories in the docker contain I stead of poi t them out side. Now when I try to update I lose ally meta data. Is there a way to move those folders before I upgrade?
https://docs.docker.com/reference/cli/docker/container/cp/
You’re just running in docker, so you’d want to make sure you map a local folder into your container (at a different location than they are already!), then get into the container and copy your files to the host’s mapped folder. Once that’s complete, update your docker to point your local folder to the proper config location and it should keep everything local after you upgrade.
Edit: In my compose, I have this line
/jellyfin/jellyfin-data:/configso you could map it to :/backup on your first boot, copy /config to /backup, then update your compose to map it to /config and you’re good to go!
Thanks. This explanation plus the docker cp link helped get this done.
Glad to hear it. I’ll be honest, I wasn’t aware of that command, I’ve just always done it the hard way and logged into the console of the container. I have this line in my .bashrc on all my docker hosts:
alias docker-console='docker exec -it "${PWD##*/}" bash'I feel like there is a way to copy stuff from docker-volumes to disk and then point docker to the folders on the disk as external volumes, I think I’ve done that at some point years back, but not sure how to do it exactly.