this post was submitted on 18 Jun 2024
18 points (90.9% liked)

Selfhosted

40183 readers
497 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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 are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 5 months ago (3 children)

How are you persisting Immich's database?

[–] [email protected] 1 points 5 months ago (2 children)

Whatever was in the v1.101.0 compose file, which seems to be a docker volume.

[–] [email protected] 2 points 5 months ago (1 children)

Did you set the UPLOAD_LOCATION variable in your .env file?

[–] [email protected] 1 points 5 months ago

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