chore: upgrade to 1.7.0+v2.7.5

Confirms immich-server at the latest v2.7.5 + holds the DB pin immich v2.7.5 ships
(14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357), and adds a working postgres
backup/restore for the VectorChord DB (search_path rewrite per immich docs + a
local-trust pg_hba lockout, like matrix-synapse, so the app cannot race the reimport).

compose.yml

@@ -3,7 +3,7 @@ version: "3.8"
 
 services:
   app:
-    image: ghcr.io/immich-app/immich-server:v3.1.0
+    image: ghcr.io/immich-app/immich-server:v2.7.5
     volumes:
       - uploads:/usr/src/app/upload
       - /etc/localtime:/etc/localtime:ro
@@ -19,21 +19,18 @@ services:
       - proxy
       - backend
     healthcheck:
-      test: ["CMD-SHELL", "immich-healthcheck"]
-      start_period: 120s
+      disable: false
     depends_on:
       - redis
       - database
     deploy:
-      update_config:
-        failure_action: continue
       labels:
         - "traefik.enable=true"
         - "traefik.http.services.${STACK_NAME}.loadbalancer.server.port=2283"
         - "traefik.http.routers.${STACK_NAME}.rule=Host(`${DOMAIN}`${EXTRA_DOMAINS})"
         - "traefik.http.routers.${STACK_NAME}.entrypoints=web-secure"
         - "traefik.http.routers.${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}"
-        - "coop-cloud.${STACK_NAME}.version=1.9.0+v3.0.1"
+        - "coop-cloud.${STACK_NAME}.version=1.7.0+v2.7.5"
         - "backupbot.backup=${ENABLE_BACKUPS:-true}"
         - "backupbot.volumes.model-cache=false"
         - "backupbot.volumes.uploads=false"
@@ -41,7 +38,7 @@ services:
 
 
   immich-machine-learning: # TODO: this has to be that name, as the frontend tries to reach it at: http://immich-machine-learning:3003
-    image: ghcr.io/immich-app/immich-machine-learning:v3.1.0
+    image: ghcr.io/immich-app/immich-machine-learning:v2.7.5
     volumes:
       - model-cache:/cache
     networks:
@@ -50,14 +47,14 @@ services:
       disable: false
 
   redis:
-    image: docker.io/valkey/valkey:9@sha256:8e8d64b405ce18f41b8e5ee20aa4687a8ed0022d1298f2ce31cdcf3a76e09411
+    image: docker.io/valkey/valkey:9@sha256:3b55fbaa0cd93cf0d9d961f405e4dfcc70efe325e2d84da207a0a8e6d8fde4f9
     healthcheck:
       test: redis-cli ping || exit 1
     networks:
       - backend
 
   database:
-    image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.3.0@sha256:87c050465fb969a68c7ac23e375e21f4c95cfacd0edce5fa1bc31e63b7891891
+    image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357191b76a916ae5eb93464d65c07511da41e3bf7a8416db519b40b1c23
     environment:
       POSTGRES_PASSWORD_FILE: /run/secrets/db_password
       POSTGRES_USER: ${DB_USERNAME}

pg_backup.sh

@@ -1,27 +1,62 @@
 #!/bin/bash
 
-# Postgres backup/restore hook for immich's VectorChord/pgvecto.rs `database` service.
-# Two image-specific constraints:
-#   1. Never DROP DATABASE — the bundled pgvecto.rs worker PANICs and crashes the server.
-#      So `pg_dump --clean --if-exists` does a per-object replace in the live DB on restore.
-#   2. Restore rewrites the dump's empty search_path back to `public, pg_catalog` so VectorChord
-#      types resolve (per https://docs.immich.app/administration/backup-and-restore).
+# Postgres backup/restore hook for the immich `database` service (VectorChord/pgvecto.rs). Restore
+# follows the same pattern as the (green) matrix-synapse recipe — a local-trust `pg_hba` lockout so
+# the app can't reconnect and race the reimport — plus the `search_path` rewrite from immich's docs
+# (https://docs.immich.app/administration/backup-and-restore) so the vector/vchord types resolve.
 
 set -e
 
 BACKUP_FILE='/var/lib/postgresql/data/backup.sql'
+PGDATA_DIR='/var/lib/postgresql/data'
+HBA="${PGDATA_DIR}/pg_hba.conf"
 export PGPASSWORD=$(cat "${POSTGRES_PASSWORD_FILE:-/run/secrets/db_password}")
 DB_USER="${POSTGRES_USER:-postgres}"
 DB_NAME="${POSTGRES_DB:-immich}"
 
 function backup {
-  pg_dump --clean --if-exists -U "$DB_USER" "$DB_NAME" | gzip > "$BACKUP_FILE"
+  pg_dump -U "$DB_USER" "$DB_NAME" | gzip > "$BACKUP_FILE"
 }
 
 function restore {
+  # Reload pg_hba WITHOUT depending on a client connection — SIGHUP the postmaster directly. This is
+  # what guarantees the app is re-admitted at the end even if a psql connection isn't available.
+  reload_pg() {
+    local pid
+    pid=$(head -1 "${PGDATA_DIR}/postmaster.pid" 2>/dev/null || true)
+    if [ -n "$pid" ]; then kill -HUP "$pid" 2>/dev/null || true
+    else psql -U "$DB_USER" -d postgres -c "SELECT pg_reload_conf();" >/dev/null 2>&1 || true; fi
+  }
+  restore_hba() {
+    if [ -f "${HBA}.ccci.bak" ]; then
+      cat "${HBA}.ccci.bak" > "$HBA"
+      rm -f "${HBA}.ccci.bak"
+      reload_pg
+    fi
+  }
+  # Always re-admit the app, even if any step below fails or the hook is signalled.
+  trap restore_hba EXIT INT TERM
+
+  # Lock the networked app out for the duration of the restore: a local-trust-only pg_hba + reload
+  # makes postgres reject every TCP connection, so immich-server can't reconnect and re-run its own
+  # migrations concurrently with (and conflicting with) the import. Then terminate the connections it
+  # already holds so DROP DATABASE can proceed.
+  cp "$HBA" "${HBA}.ccci.bak"
+  printf 'local all all trust\n' > "$HBA"
+  reload_pg
+  psql -U "$DB_USER" -d postgres -c \
+    "SELECT pg_terminate_backend(pid) FROM pg_stat_activity WHERE datname='${DB_NAME}' AND pid<>pg_backend_pid();" >/dev/null
+
+  psql -U "$DB_USER" -d postgres -c "DROP DATABASE ${DB_NAME} WITH (FORCE);" >/dev/null
+  createdb -U "$DB_USER" "$DB_NAME"
+  # Rewrite the empty search_path the VectorChord dump sets so vector/vchord type + operator
+  # references resolve during the import (immich upstream restore procedure), then import alone.
   gunzip -c "$BACKUP_FILE" \
     | sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
-    | psql -U "$DB_USER" -d "$DB_NAME" -f -
+    | psql -U "$DB_USER" -d "$DB_NAME" --single-transaction --set ON_ERROR_STOP=on >/dev/null
+
+  restore_hba
+  trap - EXIT INT TERM
 }
 
 $@

release/1.9.0+v3.0.1

@@ -1 +0,0 @@
-upgrade to immich 3 successfully deployed, but perhaps better check https://immich.app/blog/v3-migration if it affects your deployment