this post was submitted on 25 May 2024
56 points (96.7% liked)

Selfhosted

40152 readers
570 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
 

Ohboy. Tonight I:

  • installed a cool docker monitoring app called dockge
  • started moving docker compose files from random other folders into one centralized place (/opt/dockers if that matters)
  • got to immich, brought the container down
  • moved the docker-compose.yml into my new folder
  • docker compose up -d
  • saw errors saying it didn't have a DB name to work with, so it created a new database

panik

  • docker compose down
  • copy old .env file from the old directory into the new folder!
  • hold breath
  • docker compose up -d

Welcome to Immich! Let's get started...

Awwwwww, crud.

Anything I can do at this point?

No immich DB backup but I do have the images themselves.

EDIT: Thanks to u/atzanteol I figured out that changing the folder name caused this too. I changed the docker folder's name back to the original name and got my DB back! yay

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 9 points 5 months ago (8 children)

Hmmm...

docker volume ls 
DRIVER    VOLUME NAME
local     1da54fed5d479f5a551aaf853999fcc3db659193df2643a2bf20470f4da06bee
local     (a bunch more like the above)
...
local     immich-app_model-cache
local     immich-app_pgdata
local     immich-app_tsdata
local     immich_model-cache
local     immich_pgdata

I'm not sure how to tell what the many volumes with names like guids could be from. (I have like 12 docker apps running here)

My docker compose yml file also has:

database:
    container_name: immich_postgres
    image: tensorchord/pgvecto-rs:pg14-v0.2.0
    env_file:
      - .env
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
    volumes:
      - pgdata:/var/lib/postgresql/data

I think my problem is that I didn't have the proper .env file the first time I started it up after moving the yml file, and that's why immich thought it neded to create a new database from scratch. Does that make sense? I think it's realy overwritten those

[–] [email protected] 17 points 5 months ago* (last edited 5 months ago) (7 children)

Is it not in the immich_pgdata or immich-app_pgdata folder?

The volumes themselves should be stored at /var/lib/docker/volumes

For future reference, doing operations like this without backing up first is insane.

Get borgmatic installed to take automatic backups and send them to a backup like another server or borgbase.

[–] [email protected] 16 points 5 months ago (6 children)

OMG! Yes!!!

I thought it would be good to make the folder name shorter when I moved it, so it went from immich-app before, to immich.

I just now brought it down, renamed the folder, brought it back up and my DB is back again!

Thank you so much. <3

I weill check out borgmatic too. Cheers,

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

Woohoo! Always great to read a success story!

load more comments (5 replies)
load more comments (5 replies)
load more comments (5 replies)