Cannot get a stable install running

[north cairn]

On Unraid, I've installed Postgres14 (tensorchord/pgvecto-rs:pg14-v0.2.0), Redis, and Immich - all installed via CA apps. I got it working day 1, then it broke and I kept having to re-create folders that the Immich container was failing to find. Got tired of doing that so I purged my Postgres database, reinstalled, and was able to backup photos again. Now, just a few days later, it breaks again failing to find certain files or folders. What am I doing wrong?

[distant lagoon]

:wave: Hey @north cairn,

Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich .

References

• Container Logs: docker compose logs docs
• Container Status: docker compose ps docs
• Reverse Proxy: https://immich.app/docs/administration/reverse-proxy

Checklist

1. :blue_square: I have verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: I have read applicable release notes.
3. :blue_square: I have reviewed the FAQs for known issues.
4. :blue_square: I have reviewed Github for known issues.
5. :blue_square: I have tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the /upload command.
7. :blue_square: I have tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

[violet citrus]

It looks like you broke your database. Base/####/#### is the postgres data structure. Are you sure you purged it properly?

[jaunty rune]

My guess is your postgres data is stored on a cache pool and the mover is destroying it

[north cairn]

I was wondering this the first time this happened because I want my DB to be fast as possible so permanently have it live on cache (correct?). I tried creating a txt file with the postgres host path as an exception to never move it off of cache. I'm assuming now that it's not working

[jaunty rune]

I'd say start by just putting it on hdd, that should be fine tbh. If you're gonna put it on the cache then do that in a share with the mover disabled entirely

[north cairn]

Will try that. Thanks for the quick response! @jaunty rune and @violet citrus