Hopefully I’m posting this in the right place. I’m planning on using immich for selfhosted photo storage. I’m a bit worried that I may lose all my photos if my drive fails, so I’m planning on running two hdd’s in raid 1 in addition to my nvme that I’m running my OS on.
I couldn’t find this when I googled it, but is it possible to point immich to store data on a separate internal drive other than the one that the OS is running on?
Yes, you can. But will you be able to keep up with their tiring update cycle that forces you to redeploy every week?
Idk, maybe? I’m a docker noob. How hard is it to redeploy a docker container and keep my photos?
Assuming you set up your volume correctly, it’s very easy. If you’re brave, you could even have your image URI use the tag
latest, then all you need to do is restart the container each time an update comes out. I’m a little less brave. I like to use explicit version numbers. I just update my Dockerfile or yml file and restart it each time.Kinda unrelated, but if I restart my computer for whatever reason, will the containers and volumes be wiped out?
Nope, the containers will stop and the volumes (bind mount or classic) will persist
The volumes will be fine. The way volumes work is the data is stored on the host in a directory, and then that directory gets mounted on the container. So as long as you don’t delete the volume’s folder on the host, you are totally fine.
The containers won’t get wiped, but even if they did, it wouldn’t matter. They aren’t anything special. You could wipe them at will and pull them again and restart them. As long as your volumes didn’t get deleted, it will be like nothing even happened.
It is not very hard. The problem is when they suddenly change an environment variable name or format, and you need to debug what is not working and why