this post was submitted on 12 Jul 2023
14 points (88.9% liked)

Selfhosted

40149 readers
593 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] skates@sh.itjust.works 1 points 1 year ago (2 children)

Idk, maybe? I'm a docker noob. How hard is it to redeploy a docker container and keep my photos?

[–] danielo515@lemmy.world 1 points 1 year ago

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

[–] dandroid@dandroid.app 1 points 1 year ago (1 children)

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.

[–] skates@sh.itjust.works 1 points 1 year ago (2 children)

Kinda unrelated, but if I restart my computer for whatever reason, will the containers and volumes be wiped out?

[–] MaggiWuerze@feddit.de 3 points 1 year ago

Nope, the containers will stop and the volumes (bind mount or classic) will persist

[–] dandroid@dandroid.app 2 points 1 year ago

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.