Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)AN
Posts
10
Comments
108
Joined
2 yr. ago

  • I don't run as root because I've always been told I shouldn't. I don't know enough about anything to be contradicting stuff like this. It has always seemed weird to me that we don't run as root and then just sudo everything, though.

    What is the reason we don't run as root?

  • 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:
    
    
      
  • 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

  • I think they're trying to say that the amount of brownie is dictated by the amount of batter you have, and you can use one tray as many times as necessary to use up all the batter