Immich•5d ago

Updating .env and compose for 1.133.0

I am trying to follow the update instructions for the breaking changes included in 1.133.0. My problem is that my docker compose database entry has the volume: - pgdata:/var/lib/postgresql/data The updated compose has : - ${DB_DATA_LOCATION}:/var/lib/postgresql/data It is clearly calling a variable from .env. Unfortunately my env has no ${DB_DATA_LOCATION} variable. I have manually backed up my database and am still on 1.132.3. I want to know what changes I should make to my .env and compose to make the update seamless. I have included the full files here.

env

docker-compose.yml

7 Replies

Immich•5d ago

:wave: Hey @cuahutecutli, 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 - Container Logs: docker compose logs docs - Container Status: docker ps -a docs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy - Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA Checklist I have... 1. :blue_square: 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. :ballot_box_with_check: uploaded the relevant information (see below). 7. :ballot_box_with_check: 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.

Zuri3l•5d ago

In my case I changed DB_DATA LOCATION to use a named volume and restored the backup using the documentation and with the following code and it solved all my problems

gunzip < ./backup/dump.sql.gz \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| docker exec -i immich_postgres psql --username=postgres

gunzip < ./backup/dump.sql.gz \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| docker exec -i immich_postgres psql --username=postgres

  database:
    container_name: immich_postgres
    image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: '--data-checksums'
      # Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs
      # DB_STORAGE_TYPE: 'HDD'
    volumes:
      # Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCATION in the .env file
      ####################named-volume#####################
      - immich_postgres_data:/var/lib/postgresql/data
    restart: always

volumes:
  model-cache:
  immich_postgres_data:
    name: immich_postgres_data

  database:
    container_name: immich_postgres
    image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: '--data-checksums'
      # Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs
      # DB_STORAGE_TYPE: 'HDD'
    volumes:
      # Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCATION in the .env file
      ####################named-volume#####################
      - immich_postgres_data:/var/lib/postgresql/data
    restart: always

volumes:
  model-cache:
  immich_postgres_data:
    name: immich_postgres_data

and my .env does not have DB_DATA_LOCATION set.

# The location where your uploaded files are stored
UPLOAD_LOCATION=/storage/immich
# The location where your database files are stored
#DB_DATA_LOCATION=./postgres
#ubicacion de las copias de seguridad
#BACKUP_LOCATION=./backup

# The location where your uploaded files are stored
UPLOAD_LOCATION=/storage/immich
# The location where your database files are stored
#DB_DATA_LOCATION=./postgres
#ubicacion de las copias de seguridad
#BACKUP_LOCATION=./backup

Daniel•5d ago

@cuahutecutli you can also leave it as is though. The release notes point out which parts you have to change. The mount point isn't one of them

cuahutecutliOP•5d ago

Okay, quick question. Is there a way to update my mount point so that it more closely aligns with the documentation? Where would the 'pgdata' be located from my compose setup? pgdata:/var/lib/postgresql/data Theoretically I could update my .env to point to my existing data and then update the compose to pull that location from the .env, correct? I just don't know where the current 'pgdata' lives.

Mraedis•5d ago

just use: DB_DATA_LOCATION=immich_postgres_data in your env if you want to use - ${DB_DATA_LOCATION}:/var/lib/postgresql/data in your compose Otherwise you'd have to rename your volume somehow and why risk that?

Immich•4d ago

This thread has been closed. To re-open, use the button below.

cuahutecutliOP•3d ago

Solution worked perfectly, I am now on 1.134.0.

Gaming

Programming

Updating .env and compose for 1.133.0

Did you find this page helpful?