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:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
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?
It's really weird. I think there are somehow two database volumes on my system.
The reason I think this is because:
upload folders. Both have a uuid as their name and one of the uuids matches with the user id in the databaseSo, where did this other user come from? Why have none of my log ins been tracked in the database before the incident?
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
The weird thing is that it's intermittent. It's only happened twice since I started using immich. I've been restarting the containers repeatedly for a few days now and it hasnt happened again.
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_LOCATION variable in your .env file?
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
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
I've no idea about the max size hypothesis. I'm simply confirming that Caddy is a proxy in this context.