That sounds like a good thing.

I must admit that I can’t think of any examples of this ever being a problem though. It might also be because I’m just so used to crappy software breaking things that I’ve just come to accept it as normal

Given other comments in this thread and the reactions I’ve seen on mastodon, people are freaking out, but I just don’t understand why. Can someone more intelligent please take the time to ELI5?

I’m using .home and have not had any issues. Would you mind sharing what problems you’ve come across so I know what to expect?

I use this and it’s been completely flawless from day one. The documentation is up there with the best I’ve seen, and the matrix room always has someone willing to help explain further

https://github.com/spantaleev/matrix-docker-ansible-deploy

I did. The local files have GPS data visible in the phone’s gallery app, but the same file in immich doesn’t have it

Over a week at this point

Done. Link here for anyone in the future who might come across this issue https://github.com/immich-app/immich/issues/11280

I’m on 1.108

Couldn’t find anything obvious in the settings either

I did, but couldn’t find anything

I think you’re missing an important aspect to containers and that is being able to easily define your infrastructure as code.

That makes server migrations a breeze

Headless. It’s all running fine in the background. For now…

I have no issue writing a compose file. Dockge offers a bit more than that with logs and buttons for common commands which makes it easier and quicker to manage than through SSH.

To each their own 🙂

This is pretty much my situation. “Away from home” for me isn’t just a trip to the shops, it means being away for weeks at a time. I need to be able to fix things remotely if needed.

I’ve seen people recommend SSH, which seems worse because that would give potential hackers access to the whole system.

VPN is a very good suggestion, and what I’ve implemented now. Thank you to everyone who contributed

It’s really weird. I think there are somehow two database volumes on my system.

The reason I think this is because:

1. I am the only user
2. there is only one user in the user table
3. there are two folders in the upload folders. Both have a uuid as their name and one of the uuids matches with the user id in the database
4. the user_token table has tokens no tokens from before this happened to me a couple days ago

So, 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.

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:

The images are definitely uploaded. They’re on the fs, and in the correct folders

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

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

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