Hello,
I’ve noticed that when I restart my docker compose stack, the app seems to think that the server doesn’t have copies of the latest files and re-uploads them.
The files can be seen in the filesystem of the host, but not through the web interface until they have been re-uploaded. The app uploads duplicates of all the files, at which point the web can see them again, and the fs has duplicates of everything.
This happens when I restart the stack, no upgrades to the system, just docker compose down and docker compose up -d
My set up is using an unmodified compose file from the docs. Any ideas what I could be doing wrong?
You must log in or # to comment.
There is an issue with your database persistence. The file is being uploaded but it’s not being recorded in your database for some reason.
Describe in detail what your hardware and software setup is, particularly the storage and OS.
You can probably check this by trying to upload something and then checking the database files to see the last modified date.
I haven’t had time to look into this, but I think this might be the right track. Is it possible for docker to get volumes mixed up? Like, could there be a duplicate dB volume and when the stack gets restarted, docker picks one or the other?
To answer your question, I’m running docker 26.1.1 on Ubuntu server 22.04.4 LTS
The system is on an ssd and the storage is a three disk raid5
Like, could there be a duplicate dB volume and when the stack gets restarted, docker picks one or the other?
I’m not sure that is possible. Once a service has a volume defined it’ll use that unless you manually change it.
But if you don’t have a volume defined, data won’t persist when the service is updated.
If you’re just using the compose stack given by Immich, then everything should be set up properly though.
The volume is defined like this at the end of the compose file
database: container_name: immich_postgres image: registry.hub.docker.com/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0 environment: POSTGRES_PASSWORD: ${DB_PASSWORD} POSTGRES_USER: ${DB_USERNAME} POSTGRES_DB: ${DB_DATABASE_NAME} volumes: - pgdata:/var/lib/postgresql/data restart: always volumes: pgdata: model-cache:Yeah that looks fine, odd.
I assume this is a pretty normal install of Ubuntu, and /var/lib/docker hasn’t been messed with at all?
That’s correct. Ubuntu is basically just a platform to run docker, haven’t really touched it. Docker is the same. Just using it to run my containers. Haven’t ventured at all into /var/lib/docker
How are you persisting Immich’s database?
Whatever was in the v1.101.0 compose file, which seems to be a docker volume.
Did you set the
UPLOAD_LOCATIONvariable in your.envfile?Yes, it is set. The files persist fine and in the right location. I think Lem453 is along the right track. I think it’s a dB issue
Are you using a web proxy? I am guessing it may be doing partials because of upload limit of the proxy.
It is sitting behind caddy, not sure if that’s considered a proxy
Yes that is a proxy.
I haven’t set a Max size, and from what I can understand in the docs, caddy doesn’t have a default Max upload
I’ve no idea about the max size hypothesis. I’m simply confirming that Caddy is a proxy in this context.
https://caddy.its-em.ma/v1/docs/limits you appear to be correct it’s something else. Reviewing logs of Immich and if the images uploaded can be accessed would be good info to start with.
The images are definitely uploaded. They’re on the fs, and in the correct folders
