2023-09-25, 03:21 PM
With containers, the only data that sticks around (persistent) is the data you have a mounted volume to store information in. If you have volumes for config and other recommended persistent data areas (all mentioned in the docs), your data will be present when you update.
You can update your container using four commands: docker stop, rm, pull, run. You need your container name or ID (you can get it using "docker ps") for the first two. The first stops the container gracefully, the second removes all non-persistent data. The third command you use the container designation you stated in your first sentence (jellyfin/jellyfin:latest). The last you need to match your original run command so that one will be the most difficult for me to mimic but hopefully you wrote it down or documented it somewhere. Should be something like this:
You can update your container using four commands: docker stop, rm, pull, run. You need your container name or ID (you can get it using "docker ps") for the first two. The first stops the container gracefully, the second removes all non-persistent data. The third command you use the container designation you stated in your first sentence (jellyfin/jellyfin:latest). The last you need to match your original run command so that one will be the most difficult for me to mimic but hopefully you wrote it down or documented it somewhere. Should be something like this:
Code:
docker stop jellyfin
docker rm jellyfin
docker pull jellyfin/jellyfin:latest
docker run -d \
--name jellyfin \
--user 1000:1000 \
--net=host \
--volume /path/to/config:/config
--volume /path/to/cache:/cache
--volume /path/to/media:/media \
--restart=unless-stopped \
jellyfin/jellyfin:latest
Jellyfin 10.9.7 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage