#Unraid Immich Instance Gone

1 messages · Page 1 of 1 (latest)

shrewd path
#

I had a problem with my Docker image on Unraid so I've had to pull down all my containers again (using the exact same configurations for each). I had Immich setup using Docker compose and I've just created it again using the exact same compose file but upon opening the web ui it is as if I am setting up from scratch. My understanding is it should have picked up all the data from the prior instance? Please help how can I resolve this?

graceful snowBOT
#

:wave: Hey @shrewd path,

Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich immich.

References

#

Checklist

I have...

  1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :ballot_box_with_check: read applicable release notes.
  3. :ballot_box_with_check: reviewed the FAQs for known issues.
  4. :ballot_box_with_check: reviewed Github for known issues.
  5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: uploaded the relevant information (see below).
  7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

Information

In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:

  • Your docker-compose.yml and .env files.
  • Logs from all the containers and their status (see above).
  • All the troubleshooting steps you've tried so far.
  • Any recent changes you've made to Immich or your system.
  • Details about your system (both software/OS and hardware).
  • Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
  • The version of the Immich server, mobile app, and other relevant pieces.
  • Any other information that you think might be relevant.

Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

shrewd path
# 
name: immich

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    extends:
      file: hwaccel.yml
      service: hwaccel
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    ports:
      - 2283:2283
    depends_on:
      - redis
      - database
    restart: always

  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    cpus: 1
    volumes:
      - model-cache:/cache
    env_file:
      - .env
    restart: always

  redis:
    container_name: immich_redis
    image: redis:6.2-alpine@sha256:3995fe6ea6a619313e31046bd3c8643f9e70f8f2b294ff82659d409b47d06abb
    restart: always

  database:
    container_name: immich_postgres
    image: tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0
    env_file:
      - .env
    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:
brave nexus
#

Do you have a backups folder in your upload_location?

shrewd path
#

yes I do

graceful snowBOT
brave nexus
#

You’ll have to restore from our docs

shrewd path
#

I

brave nexus
#

Might be good to switch Postgres to a bind mount folder while you’re at it

blissful gorge
#

To clarify exactly what the problem was:

    volumes:
      - pgdata:/var/lib/postgresql/data
#

Pgdata is a docker volume

#

And so was stored in the docker image you removed

shrewd path
#

I've looked at this but I don't quite even understand the first command in the restore. The output from it in the unraid window is: no configuration file provided: not found

shrewd path
blissful gorge
shrewd path
#

ahh that makes sense

brave nexus
#

You can take an example from our current docker compose file

shrewd path
#

I'll have a look

#

Would you recommend replacing my current compose file with the most recent example one?