PostgresError: column "sidecarPath" does not exist when upgrade from 1.135.3 to 1.136

[kiritoxjf]

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

• Yes

The bug

After upgrade, docker container can not start normally. After I checkout the docker logs, it show that UPDATE "asset" SET "sidecarPath" = REGEXP_REPLACE("sidecarPath", '^upload', '/usr/src/app/upload') WHERE "sidecarPath" IS NOT NULL. It get the error "PostgresError: column "sidecarPath" does not exist".

The OS that Immich Server is running on

Unraid

Version of Immich Server

v1.136

Version of Immich Mobile App

v1.135.1

Platform with the issue

• Server
• Web
• Mobile

Your docker-compose.yml content

services:
  immich-server:
    container_name: immich_server
    image: ghcr.nju.edu.cn/immich-app/immich-server:release
    environment:
      PUID: 1000
      PGID: 100
      DB_HOSTNAME: immich_postgres
      DB_PORT: 5432
      DB_DATABASE_NAME: immich
      DB_USERNAME: xxxx
      DB_PASSWORD: xxxx
      REDIS_HOSTNAME: immich_redis
      REDIS_PORT: 6379
      TZ: Asia/Shanghai
    volumes:
      - /mnt/user/appdata/immich/upload:/usr/src/app/upload
    ports:
      - '2283:2283'
    depends_on:
      - immich_redis
      - immich_postgres
    restart: always
    healthcheck:
      disable: false
    runtime: nvidia
    devices:
      - "/dev/nvidia0:/dev/nvidia0"
      - "/dev/nvidiactl:/dev/nvidiactl"
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              count: 1
              capabilities:
                - gpu

Your .env content

without env file

Reproduction steps

1.docker-compose pull
2.docker-compose up -d
3.
...

Relevant log output

Additional information

[kiritoxjf]

I checked the database table columns, I found that it add a new column called sidecarPath from 1.135 to 1.136. And I exec into the container, add the column to table asset using SQL shell ALTER TABLE asset ADD "sidecarPath" varchar. After that, the application runs normally.

[deThommy]

same problem regarding various fields and their names in the postgre database in other threads after updating from 1.135.3 to 1.136 which leads to immich being unable to start

happens with proxmox helper-script or update command after installing through helper-script

[skatsubo]

A lot of stuff in the database was touched/renamed/updated in recent Immich versions 1.135-1.137.
These DB changes uncovered some setups having various lingering DB schema drifts: extraneous or missing tables, indexes, constraints, triggers... Now, in this case, a missing column.
Those drifts may be due to limited transactional control of DB migrations in earlier Immich versions. As @deThommy pointed out, custom install/update scripts may be involved as well.

I'm going to convert this issue into discussion.
@kiritoxjf If you have successfully solved it by adding the column, then feel free to close this discussion.