Hey everyone! I've got a home-server that uses a ZFS pool for storage, which acts as my NAS. In this ZFS pool, I have a designated folder located at /rastla-nas/private/.docker. Inside this folder, I've organized separate directories for Jellyfin, Immich, and other Docker-backed applications. Each of these has its own ./data folder that's mounted, along with a docker-compose.yml file.
Now, I'm wondering, if I ever need to swap out the main SSD of my server, will I be able to just run 'docker compose up' without issues? I have a feeling that some configuration files or important data might be stored locally on the server, rather than in the mounted data folders. I really want to ensure that everything necessary is saved on the NAS. I don't mind pulling the Docker images again, but things like the metadata for Immich are really crucial for me. What settings should I adjust to achieve this?
1 Answer
You're on the right track! The beauty of Docker volumes and mounts is that they let you keep your data safe and persistent, even if you move or replace your containers. As long as your mounts point to the NAS correctly, you shouldn't run into issues when changing your SSD.
Basically, aside from the volumes and mounts, Docker doesn’t keep anything you wouldn't expect to be reusable, so your containers are generally safe to move around. Just make sure you've mapped your data directories properly in your docker-compose.yml, and everything should be set!
Yep! Setting it up right means you can swap your SSD whenever you want without losing crucial data. Just keep track of how Jellyfin and Immich store their data!
Absolutely! You can definitely add the necessary mounts to your docker-compose.yml later on without breaking anything. Just make sure the paths correctly point to where the data should be on your NAS.