Immich goes through Initial Setup if I Reboot VM
Quick insight to my setup:
I'm on Proxmox. I have a container with ID 200 that manages my zsataraid as a NAS. It's in zraid1 and effectively gives me 30 TB of storage.
Immich in a container wasn't working no matter what I tried, so I made a VM for immich running ubuntu server 24.04. host name is immich-server, username is immich. I mount the NAS at /mnt/fileserver using fstab. I keep the .env and composer-compose.yml at /immich-app.
Using ls -l I can see that my folder with the docker compose files is readable and writable as root, but only readable as anything else.
It took several reboots and many time logging in again on the app to get the app to let me actually press the "backup now" button.
Here's the real brain teaser
"sudo docker compose pull" could never full bring down the containers. So when I made a change to .env, I rebooted the VM. And when I got back into the web UI, it would take me through initial setup all over again.
in .env, I did set these
UPLOAD_LOCATION=/mnt/fileserver/media/immich
VERSION=1.135.1
It was after changing VERSION from release to 1.135.1 that my app finally seemed to start working as expected. I have not made any changes to docker-compose.yml as it's not recommended and I am not using hardware accelleration.
I have been told that i'm taken through initial setup again because the db file can't be found. Should I make the folder writable for non-root users? Should I just change the location to somewhere else?
---
Server: repurposed desktop parts running Proxmox. Immich is in a VM, not a container. 4 (logical) cores, 8 gigs of ram
Phone: Pixel 8 Pro
Immich version: 1.135.3 (I tried to force 1.135.1, but it didn't change anything)
Immich app version: 1.135.1 (I'm told this is the latest and that the app may be a bit behind)
I'm on Proxmox. I have a container with ID 200 that manages my zsataraid as a NAS. It's in zraid1 and effectively gives me 30 TB of storage.
Immich in a container wasn't working no matter what I tried, so I made a VM for immich running ubuntu server 24.04. host name is immich-server, username is immich. I mount the NAS at /mnt/fileserver using fstab. I keep the .env and composer-compose.yml at /immich-app.
Using ls -l I can see that my folder with the docker compose files is readable and writable as root, but only readable as anything else.
It took several reboots and many time logging in again on the app to get the app to let me actually press the "backup now" button.
Here's the real brain teaser
"sudo docker compose pull" could never full bring down the containers. So when I made a change to .env, I rebooted the VM. And when I got back into the web UI, it would take me through initial setup all over again.
in .env, I did set these
UPLOAD_LOCATION=/mnt/fileserver/media/immich
VERSION=1.135.1
It was after changing VERSION from release to 1.135.1 that my app finally seemed to start working as expected. I have not made any changes to docker-compose.yml as it's not recommended and I am not using hardware accelleration.
I have been told that i'm taken through initial setup again because the db file can't be found. Should I make the folder writable for non-root users? Should I just change the location to somewhere else?
---
Server: repurposed desktop parts running Proxmox. Immich is in a VM, not a container. 4 (logical) cores, 8 gigs of ram
Phone: Pixel 8 Pro
Immich version: 1.135.3 (I tried to force 1.135.1, but it didn't change anything)
Immich app version: 1.135.1 (I'm told this is the latest and that the app may be a bit behind)
