immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-07-25 14:00:45 +03:00
Code Issues 783 Packages Projects Releases 22 Wiki Activity

Lost database upgrading from v1.140.1 to v1.142.0 #7175

New Issue
Closed
opened 2026-02-05 12:50:27 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-05 12:50:27 +03:00
Owner
Copy Link

Originally created by @kelter-antunes on GitHub (Sep 13, 2025).

I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.

  • Yes

The bug

I always use the default compose file, with the default .env file, except the passwords. Always upgraded successfully, but this time I got a "database reset". Already connected to Postgres docker, checked database tables, all empty.

The OS that Immich Server is running on

Debian 12

Version of Immich Server

v1.142.0

Version of Immich Mobile App

v1.142.0

Platform with the issue

  • Server
  • Web
  • Mobile

Device make and model

No response

Your docker-compose.yml content

#
# WARNING: To install Immich, follow our guide: https://immich.app/docs/install/docker-compose
#
# Make sure to use the docker-compose.yml of the current release:
#
# https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml
#
# The compose file on main may not be compatible with the latest release.

name: immich

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    # extends:
    #   file: hwaccel.transcoding.yml
    #   service: cpu # set to one of [nvenc, quicksync, rkmpp, vaapi, vaapi-wsl] for accelerated transcoding
    volumes:
      # Do not edit the next line. If you want to change the media storage location on your system, edit the value of UPLOAD_LOCATION in the .env file
      - ${UPLOAD_LOCATION}:/data
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - stack.env
    ports:
      - '2283:2283'
    depends_on:
      - redis
      - database
    restart: always
    healthcheck:
      disable: false

  immich-machine-learning:
    container_name: immich_machine_learning
    # For hardware acceleration, add one of -[armnn, cuda, rocm, openvino, rknn] to the image tag.
    # Example tag: ${IMMICH_VERSION:-release}-cuda
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    # extends: # uncomment this section for hardware acceleration - see https://immich.app/docs/features/ml-hardware-acceleration
    #   file: hwaccel.ml.yml
    #   service: cpu # set to one of [armnn, cuda, rocm, openvino, openvino-wsl, rknn] for accelerated inference - use the `-wsl` version for WSL2 where applicable
    volumes:
      - model-cache:/cache
    env_file:
      - stack.env
    restart: always
    healthcheck:
      disable: false

  redis:
    container_name: immich_redis
    image: docker.io/valkey/valkey:8-bookworm@sha256:fea8b3e67b15729d4bb70589eb03367bab9ad1ee89c876f54327fc7c6e618571
    healthcheck:
      test: redis-cli ping || exit 1
    restart: always

  database:
    container_name: immich_postgres
    image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:8d292bdb796aa58bbbaa47fe971c8516f6f57d6a47e7172e62754feb6ed4e7b0
    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
      - ${DB_DATA_LOCATION}:/var/lib/postgresql/data
    shm_size: 128mb
    restart: always

volumes:
  model-cache:

Your .env content

UPLOAD_LOCATION=/mnt/share
DB_DATA_LOCATION=./postgres
IMMICH_VERSION=release
DB_PASSWORD=#########
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

Reproduction steps

I just updated the stack via portainer

Relevant log output

Additional information

No response

Originally created by @kelter-antunes on GitHub (Sep 13, 2025). ### I have searched the existing issues, both open and closed, to make sure this is not a duplicate report. - [x] Yes ### The bug I always use the default compose file, with the default .env file, except the passwords. Always upgraded successfully, but this time I got a "database reset". Already connected to Postgres docker, checked database tables, all empty. ### The OS that Immich Server is running on Debian 12 ### Version of Immich Server v1.142.0 ### Version of Immich Mobile App v1.142.0 ### Platform with the issue - [x] Server - [ ] Web - [ ] Mobile ### Device make and model _No response_ ### Your docker-compose.yml content ```YAML # # WARNING: To install Immich, follow our guide: https://immich.app/docs/install/docker-compose # # Make sure to use the docker-compose.yml of the current release: # # https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml # # The compose file on main may not be compatible with the latest release. name: immich services: immich-server: container_name: immich_server image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release} # extends: # file: hwaccel.transcoding.yml # service: cpu # set to one of [nvenc, quicksync, rkmpp, vaapi, vaapi-wsl] for accelerated transcoding volumes: # Do not edit the next line. If you want to change the media storage location on your system, edit the value of UPLOAD_LOCATION in the .env file - ${UPLOAD_LOCATION}:/data - /etc/localtime:/etc/localtime:ro env_file: - stack.env ports: - '2283:2283' depends_on: - redis - database restart: always healthcheck: disable: false immich-machine-learning: container_name: immich_machine_learning # For hardware acceleration, add one of -[armnn, cuda, rocm, openvino, rknn] to the image tag. # Example tag: ${IMMICH_VERSION:-release}-cuda image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release} # extends: # uncomment this section for hardware acceleration - see https://immich.app/docs/features/ml-hardware-acceleration # file: hwaccel.ml.yml # service: cpu # set to one of [armnn, cuda, rocm, openvino, openvino-wsl, rknn] for accelerated inference - use the `-wsl` version for WSL2 where applicable volumes: - model-cache:/cache env_file: - stack.env restart: always healthcheck: disable: false redis: container_name: immich_redis image: docker.io/valkey/valkey:8-bookworm@sha256:fea8b3e67b15729d4bb70589eb03367bab9ad1ee89c876f54327fc7c6e618571 healthcheck: test: redis-cli ping || exit 1 restart: always database: container_name: immich_postgres image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:8d292bdb796aa58bbbaa47fe971c8516f6f57d6a47e7172e62754feb6ed4e7b0 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 - ${DB_DATA_LOCATION}:/var/lib/postgresql/data shm_size: 128mb restart: always volumes: model-cache: ``` ### Your .env content ```Shell UPLOAD_LOCATION=/mnt/share DB_DATA_LOCATION=./postgres IMMICH_VERSION=release DB_PASSWORD=######### DB_USERNAME=postgres DB_DATABASE_NAME=immich ``` ### Reproduction steps I just updated the stack via portainer ### Relevant log output ```shell ``` ### Additional information _No response_
OVERLORD commented 2026-02-05 12:50:29 +03:00
Author
Owner
Copy Link

@bo0tzz commented on GitHub (Sep 13, 2025):

I always use the default compose file, with the default .env file

Do you mean by this that you copy over the compose file from the release each time? Because you shouldn't do that, you should read the release notes and just make the changes mentioned in there.

@bo0tzz commented on GitHub (Sep 13, 2025): > I always use the default compose file, with the default .env file Do you mean by this that you copy over the compose file from the release each time? Because you shouldn't do that, you should read the release notes and just make the changes mentioned in there.
OVERLORD commented 2026-02-05 12:50:30 +03:00
Author
Owner
Copy Link

@GregFurnival commented on GitHub (Sep 13, 2025):

Similar setup, my server is behind a version or two, one iPhone is 1.141 and works fine. The other is 1.142 and I am unable to see pictures after migration. Logging into browser and all pictures good to go for all accounts.

@GregFurnival commented on GitHub (Sep 13, 2025): Similar setup, my server is behind a version or two, one iPhone is 1.141 and works fine. The other is 1.142 and I am unable to see pictures after migration. Logging into browser and all pictures good to go for all accounts.
OVERLORD commented 2026-02-05 12:50:31 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Sep 13, 2025):

@GregFurnival Logout and log back in will fix the issue

@alextran1502 commented on GitHub (Sep 13, 2025): @GregFurnival Logout and log back in will fix the issue
OVERLORD commented 2026-02-05 12:50:32 +03:00
Author
Owner
Copy Link

@kelter-antunes commented on GitHub (Sep 13, 2025):

I always use the default compose file, with the default .env file

Do you mean by this that you copy over the compose file from the release each time? Because you shouldn't do that, you should read the release notes and just make the changes mentioned in there.

I always check for breaking changes before every update. If none exist, I just copy the default docker, compare and merge with the previous to make sure no new environment variable was added or removed, etc.

This time, not sure why, it wiped out all the database.

@kelter-antunes commented on GitHub (Sep 13, 2025): > > I always use the default compose file, with the default .env file > > Do you mean by this that you copy over the compose file from the release each time? Because you shouldn't do that, you should read the release notes and just make the changes mentioned in there. I always check for breaking changes before every update. If none exist, I just copy the default docker, compare and merge with the previous to make sure no new environment variable was added or removed, etc. This time, not sure why, it wiped out all the database.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:skip
changelog:translation
cli
date-time
dependencies
documentation
external-library
format
good first issue
mobile-beta
mobile-beta
mobile-beta
needs-answer
nice to have
pull-request
Mirrored from GitHub Pull Request
 sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#7175
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?