FIX: Immich resetting every reboot on Unraid.

TL;DR: Check your Postgres appdata location and make sure it's NOT saving it to cache.

Decided to post another fix for an issue I came across today because I couldn't find the answer online and it took me an embarrassing amount of time to figure this out myself (about an hour).

So I already have Immich installed, and as I've made very clear in multiple posts on this blog, it's awesome. So awesome, that I decided to setup my parents an Unraid server and of course install Immich.

Blasting through the install of the needed Docker containers (Immich, Redis, Postgres/pgvector), I had everything up and running, transferred some pictures to Immich, rebooted the Unraid server to ensure it would come back up without issues, booted back into Immich to be greeted with... a "WELCOME TO IMMICH" screen.

Ya, turns out, the DEFAULT settings for the Postgres Docker container, at least at the time of me writing this, is to save your Postgres appdata to cache. Which, as you'd imagine, clears itself at reboot.

Who would've thought that Immich doesn't like when it's database gets purged?

So ya. Very easy fix. Just change the appdata location to.. well.. literally anywhere else.

I have no clue why it now defaults to that location. Perhaps unintentional? Either way, if you're like me and didn't read the compose file line for line and figured it would throw the appdata to the proper default folder and you're having these issues, check to see where the Postgres appdata is actually being saved to.

This site works best in Firefox