Merge pull request #2805 from alexbelgium/claude/immich-addons-v3-1cgj5x

Immich: migrate immich, immich_cuda, immich_noml and immich_openvino to Immich v3

immich/CHANGELOG.md

@@ -1,3 +1,9 @@
+## 3.0.1 (2026-07-04)
+- Migrate to Immich v3 (now based on the `ghcr.io/imagegenius/immich:3` image line, tracking the v3 major release)
+- Immich v3 requires the VectorChord (`vchord`) Postgres extension; upstream `pgvecto.rs` support has been removed. Use this repository's `Postgres 15`/`Postgres 17` add-ons (or another VectorChord-capable Postgres), and let Immich finish migrating existing data before the old extension is removed
+- Immich v3 requires an x86-64-v2 (or newer) CPU on amd64
+- Migration guide: https://immich.app/blog/v3-migration
+
 ## 2.7.5-2 (21-05-2026)
 - Minor bugs fixed
 

immich/README.md

@@ -34,9 +34,19 @@ _Thanks to everyone having starred my repo! To star it click on the image below,
 Web based files browser.
 This addon is based on the [docker image](https://github.com/imagegenius/docker-immich) from imagegenius.
 
+## Immich v3
+
+This add-on tracks **Immich v3** (built on the `ghcr.io/imagegenius/immich:3` image line).
+
+- **Database**: Immich v3 requires PostgreSQL (14–17) with the **VectorChord (`vchord`)** extension; upstream `pgvecto.rs` support has been removed. The `Postgres 15` and `Postgres 17` add-ons in this repository already provide a VectorChord-capable database and are the recommended choice (you can also use the official `ghcr.io/immich-app/postgres:*-vectorchord*` image).
+- **Upgrading from Immich v2**: keep your existing VectorChord-capable database so Immich can migrate its data automatically. If your database still holds data in the old `pgvecto.rs` extension, leave that extension in place until Immich has finished migrating to VectorChord.
+- **CPU**: on `amd64`, Immich v3 requires an x86-64-v2 (or newer) CPU.
+
+See the official [v3 migration guide](https://immich.app/blog/v3-migration) for details.
+
 ## Configuration
 
-Webui can be found at `<your-ip>:8080`. PostgreSQL/MySQL can be either internal or external.
+Webui can be found at `<your-ip>:8080`. PostgreSQL can be either internal or external.
 
 ### Options
 

immich/build.json

@@ -1,6 +1,6 @@
 {
   "build_from": {
-    "aarch64": "ghcr.io/imagegenius/immich:latest",
+    "aarch64": "ghcr.io/imagegenius/immich:3",
-    "amd64": "ghcr.io/imagegenius/immich:latest"
+    "amd64": "ghcr.io/imagegenius/immich:3"
   }
 }

immich/config.yaml

@@ -137,12 +137,10 @@ schema:
   localdisks: str?
   networkdisks: str?
   skip_permissions_check: bool?
-services:
-  - mysql:want
 slug: immich
 udev: true
 url: https://github.com/alexbelgium/hassio-addons
 usb: true
-version: "2.7.5-2"
+version: "3.0.1"
 video: true
 webui: http://[HOST]:[PORT:8080]

immich/rootfs/etc/cont-init.d/99-run.sh

@@ -144,28 +144,31 @@ EOF
     bashio::log.info "Database setup completed successfully."
 }
 
-# Function to check if vectors extension is enabled
+# Function to check if the vectors (pgvecto.rs) extension is available on the server
 check_vector_extension() {
-    echo "Checking if 'vectors' extension is enabled..."
+    echo "Checking if 'vectors' extension is available for database '${DB_DATABASE_NAME}'..."
-    RESULT=$(psql "postgres://$DB_USERNAME:$DB_PASSWORD@$DB_HOSTNAME:$DB_PORT" -tAc "SELECT extname FROM pg_extension WHERE extname = 'vectors';")
+    RESULT=$(psql "postgres://$DB_USERNAME:$DB_PASSWORD@$DB_HOSTNAME:$DB_PORT/${DB_DATABASE_NAME}" -tAc "SELECT 1 FROM pg_available_extensions WHERE name = 'vectors';")
-    if [[ "$RESULT" == "vectors" ]]; then
+    if [[ "$RESULT" == "1" ]]; then
-        echo "✅ 'vectors' extension is enabled."
+        echo "✅ 'vectors' extension is available."
         return 0
     else
-        bashio::log.warning "❌ 'vectors' extension is NOT enabled."
+        bashio::log.warning "❌ 'vectors' extension is NOT available."
         return 1
     fi
 }
 
-# Function to check if vchord extension is enabled
+# Function to check if the VectorChord (vchord) extension is available on the server.
+# Uses pg_available_extensions (whether the extension CAN be created) rather than
+# pg_extension (whether it has already been created), since Immich creates the extension
+# itself on first startup; checking pg_extension would false-warn on every fresh install.
 check_vchord_extension() {
-    echo "Checking if 'vchord' extension is enabled..."
+    echo "Checking if 'vchord' extension is available for database '${DB_DATABASE_NAME}'..."
-    RESULT=$(psql "postgres://$DB_USERNAME:$DB_PASSWORD@$DB_HOSTNAME:$DB_PORT" -tAc "SELECT extname FROM pg_extension WHERE extname = 'vchord';")
+    RESULT=$(psql "postgres://$DB_USERNAME:$DB_PASSWORD@$DB_HOSTNAME:$DB_PORT/${DB_DATABASE_NAME}" -tAc "SELECT 1 FROM pg_available_extensions WHERE name = 'vchord';")
-    if [[ "$RESULT" == "vchord" ]]; then
+    if [[ "$RESULT" == "1" ]]; then
-        echo "✅ 'vchord' extension is enabled."
+        echo "✅ 'vchord' extension is available."
         return 0
     else
-        bashio::log.warning "❌ 'vchord' extension is NOT enabled."
+        bashio::log.warning "❌ 'vchord' extension is NOT available."
         return 1
     fi
 }
@@ -193,4 +196,18 @@ migrate_database
 export_db_env
 setup_root_user
 setup_database
-# check_vchord_extension || check_vector_extension
+
+# Immich v3 requires the VectorChord ('vchord') extension and no longer supports
+# 'pgvecto.rs'. Warn (non-fatally) when the external database does not expose it, so users
+# get a clear diagnostic instead of an opaque Immich startup failure. Immich creates and
+# validates the extension itself, so we never stop the addon here.
+if ! check_vchord_extension; then
+    bashio::log.warning "------------------------------------------------------------"
+    bashio::log.warning "Immich v3 requires the VectorChord ('vchord') PostgreSQL extension."
+    bashio::log.warning "Support for 'pgvecto.rs' has been removed upstream."
+    bashio::log.warning "Use the 'Postgres 15'/'Postgres 17' add-ons from this repository,"
+    bashio::log.warning "or another VectorChord-capable PostgreSQL image."
+    bashio::log.warning "Immich will attempt to create the extension itself on startup."
+    bashio::log.warning "Migration guide: https://immich.app/blog/v3-migration"
+    bashio::log.warning "------------------------------------------------------------"
+fi

immich/updater.json

@@ -1,10 +1,10 @@
 {
   "github_beta": "false",
-  "github_exclude": "2026",
+  "github_exclude": "",
-  "last_update": "2026-05-19",
+  "last_update": "2026-07-04",
   "repository": "alexbelgium/hassio-addons",
   "slug": "immich",
   "source": "github",
-  "upstream_repo": "imagegenius/docker-immich",
+  "upstream_repo": "immich-app/immich",
-  "upstream_version": "2.7.5"
+  "upstream_version": "3.0.1"
 }

immich_cuda/CHANGELOG.md

@@ -1,4 +1,10 @@
 
+## 3.0.1 (2026-07-04)
+- Migrate to Immich v3 (now based on the `ghcr.io/imagegenius/immich:3-cuda` image line, tracking the v3 major release)
+- Immich v3 requires the VectorChord (`vchord`) Postgres extension; upstream `pgvecto.rs` support has been removed. Use this repository's `Postgres 15`/`Postgres 17` add-ons (or another VectorChord-capable Postgres), and let Immich finish migrating existing data before the old extension is removed
+- Immich v3 requires an x86-64-v2 (or newer) CPU on amd64
+- Migration guide: https://immich.app/blog/v3-migration
+
 ## 2.7.5 (2026-05-19)
 - Update to latest version from imagegenius/docker-immich (changelog : https://github.com/imagegenius/docker-immich/releases)
 

immich_cuda/README.md

@@ -35,6 +35,16 @@ Self-hosted photo and video backup solution directly from your mobile phone with
 
 This addon is based on the [docker image](https://github.com/imagegenius/docker-immich) from imagegenius with CUDA support enabled for enhanced performance.
 
+## Immich v3
+
+This add-on tracks **Immich v3** (built on the `ghcr.io/imagegenius/immich:3-cuda` image line).
+
+- **Database**: Immich v3 requires PostgreSQL (14–17) with the **VectorChord (`vchord`)** extension; upstream `pgvecto.rs` support has been removed. The `Postgres 15` and `Postgres 17` add-ons in this repository already provide a VectorChord-capable database and are the recommended choice (you can also use the official `ghcr.io/immich-app/postgres:*-vectorchord*` image).
+- **Upgrading from Immich v2**: keep your existing VectorChord-capable database so Immich can migrate its data automatically. If your database still holds data in the old `pgvecto.rs` extension, leave that extension in place until Immich has finished migrating to VectorChord.
+- **CPU**: on `amd64`, Immich v3 requires an x86-64-v2 (or newer) CPU.
+
+See the official [v3 migration guide](https://immich.app/blog/v3-migration) for details.
+
 ## Hardware Requirements
 
 - **NVIDIA GPU**: Compatible NVIDIA graphics card with CUDA support

immich_cuda/build.json

@@ -1,5 +1,5 @@
 {
   "build_from": {
-    "amd64": "ghcr.io/imagegenius/immich:cuda"
+    "amd64": "ghcr.io/imagegenius/immich:3-cuda"
   }
 }

immich_cuda/config.yaml

@@ -135,12 +135,10 @@ schema:
   localdisks: str?
   networkdisks: str?
   skip_permissions_check: bool?
-services:
-  - mysql:want
 slug: immich_cuda
 udev: true
 url: https://github.com/alexbelgium/hassio-addons
 usb: true
-version: "2.7.5"
+version: "3.0.1"
 video: true
 webui: http://[HOST]:[PORT:8080]

immich_cuda/updater.json

@@ -1,10 +1,10 @@
 {
   "github_beta": "false",
-  "github_exclude": "2026",
+  "github_exclude": "",
-  "last_update": "2026-05-19",
+  "last_update": "2026-07-04",
   "repository": "alexbelgium/hassio-addons",
   "slug": "immich",
   "source": "github",
-  "upstream_repo": "imagegenius/docker-immich",
+  "upstream_repo": "immich-app/immich",
-  "upstream_version": "2.7.5"
+  "upstream_version": "3.0.1"
 }

immich_noml/CHANGELOG.md

@@ -1,4 +1,10 @@
 
+## 3.0.1 (2026-07-04)
+- Migrate to Immich v3 (now based on the `ghcr.io/imagegenius/immich:3-noml` image line, tracking the v3 major release)
+- This add-on ships without machine learning; the VectorChord (`vchord`) Postgres extension is still required by Immich v3, while upstream `pgvecto.rs` support has been removed. Use this repository's `Postgres 15`/`Postgres 17` add-ons (or another VectorChord-capable Postgres), and let Immich finish migrating existing data before the old extension is removed
+- Immich v3 requires an x86-64-v2 (or newer) CPU on amd64
+- Migration guide: https://immich.app/blog/v3-migration
+
 ## 2.7.5 (2026-05-22)
 - Update to latest version from imagegenius/docker-immich (changelog : https://github.com/imagegenius/docker-immich/releases)
 

immich_noml/README.md

@@ -35,6 +35,16 @@ Self-hosted photo and video backup solution directly from your mobile phone. Thi
 
 This addon is based on the [docker image](https://github.com/imagegenius/docker-immich) from imagegenius with machine learning components excluded to reduce resource consumption and improve compatibility with resource-constrained systems.
 
+## Immich v3
+
+This add-on tracks **Immich v3** (built on the `ghcr.io/imagegenius/immich:3-noml` image line). Machine learning is excluded, but the database requirement below still applies.
+
+- **Database**: Immich v3 requires PostgreSQL (14–17) with the **VectorChord (`vchord`)** extension; upstream `pgvecto.rs` support has been removed. The `Postgres 15` and `Postgres 17` add-ons in this repository already provide a VectorChord-capable database and are the recommended choice (you can also use the official `ghcr.io/immich-app/postgres:*-vectorchord*` image).
+- **Upgrading from Immich v2**: keep your existing VectorChord-capable database so Immich can migrate its data automatically. If your database still holds data in the old `pgvecto.rs` extension, leave that extension in place until Immich has finished migrating to VectorChord.
+- **CPU**: on `amd64`, Immich v3 requires an x86-64-v2 (or newer) CPU.
+
+See the official [v3 migration guide](https://immich.app/blog/v3-migration) for details.
+
 ## Use Cases
 
 The NoML variant is ideal for:

immich_noml/build.json

@@ -1,6 +1,6 @@
 {
   "build_from": {
-    "aarch64": "ghcr.io/imagegenius/immich:noml",
+    "aarch64": "ghcr.io/imagegenius/immich:3-noml",
-    "amd64": "ghcr.io/imagegenius/immich:noml"
+    "amd64": "ghcr.io/imagegenius/immich:3-noml"
   }
 }

immich_noml/config.yaml

@@ -136,12 +136,10 @@ schema:
   localdisks: str?
   networkdisks: str?
   skip_permissions_check: bool?
-services:
-  - mysql:want
 slug: immich_noml
 udev: true
 url: https://github.com/alexbelgium/hassio-addons
 usb: true
-version: "2.7.5"
+version: "3.0.1"
 video: true
 webui: http://[HOST]:[PORT:8080]

immich_noml/updater.json

@@ -1,10 +1,10 @@
 {
   "github_beta": "false",
-  "github_exclude": "2026",
+  "github_exclude": "",
-  "last_update": "2026-05-22",
+  "last_update": "2026-07-04",
   "repository": "alexbelgium/hassio-addons",
   "slug": "immich",
   "source": "github",
-  "upstream_repo": "imagegenius/docker-immich",
+  "upstream_repo": "immich-app/immich",
-  "upstream_version": "2.7.5"
+  "upstream_version": "3.0.1"
 }

immich_openvino/CHANGELOG.md

@@ -1,3 +1,9 @@
+## 3.0.1 (2026-07-04)
+- Migrate to Immich v3 (now based on the `ghcr.io/imagegenius/immich:3-openvino` image line, tracking the v3 major release)
+- Immich v3 requires the VectorChord (`vchord`) Postgres extension; upstream `pgvecto.rs` support has been removed. Use this repository's `Postgres 15`/`Postgres 17` add-ons (or another VectorChord-capable Postgres), and let Immich finish migrating existing data before the old extension is removed
+- Immich v3 requires an x86-64-v2 (or newer) CPU on amd64
+- Migration guide: https://immich.app/blog/v3-migration
+
 ## 2.7.5-2 (21-05-2026)
 - Minor bugs fixed
 

immich_openvino/README.md

@@ -35,6 +35,16 @@ Self-hosted photo and video backup solution directly from your mobile phone with
 
 This addon is based on the [docker image](https://github.com/imagegenius/docker-immich) from imagegenius with OpenVINO support enabled for enhanced performance on Intel hardware.
 
+## Immich v3
+
+This add-on tracks **Immich v3** (built on the `ghcr.io/imagegenius/immich:3-openvino` image line).
+
+- **Database**: Immich v3 requires PostgreSQL (14–17) with the **VectorChord (`vchord`)** extension; upstream `pgvecto.rs` support has been removed. The `Postgres 15` and `Postgres 17` add-ons in this repository already provide a VectorChord-capable database and are the recommended choice (you can also use the official `ghcr.io/immich-app/postgres:*-vectorchord*` image).
+- **Upgrading from Immich v2**: keep your existing VectorChord-capable database so Immich can migrate its data automatically. If your database still holds data in the old `pgvecto.rs` extension, leave that extension in place until Immich has finished migrating to VectorChord.
+- **CPU**: on `amd64`, Immich v3 requires an x86-64-v2 (or newer) CPU.
+
+See the official [v3 migration guide](https://immich.app/blog/v3-migration) for details.
+
 ## Hardware Requirements
 
 - **Intel Hardware**: Compatible Intel CPU or Intel integrated/discrete GPU

immich_openvino/build.json

@@ -1,5 +1,5 @@
 {
   "build_from": {
-    "amd64": "ghcr.io/imagegenius/immich:openvino"
+    "amd64": "ghcr.io/imagegenius/immich:3-openvino"
   }
 }

immich_openvino/config.yaml

@@ -136,12 +136,10 @@ schema:
   localdisks: str?
   networkdisks: str?
   skip_permissions_check: bool?
-services:
-  - mysql:want
 slug: immich_openvino
 udev: true
 url: https://github.com/alexbelgium/hassio-addons
 usb: true
-version: "2.7.5-2"
+version: "3.0.1"
 video: true
 webui: http://[HOST]:[PORT:8080]

immich_openvino/updater.json

@@ -1,10 +1,10 @@
 {
   "github_beta": "false",
-  "github_exclude": "2026",
+  "github_exclude": "",
-  "last_update": "2026-04-18",
+  "last_update": "2026-07-04",
   "repository": "alexbelgium/hassio-addons",
   "slug": "immich",
   "source": "github",
-  "upstream_repo": "imagegenius/docker-immich",
+  "upstream_repo": "immich-app/immich",
-  "upstream_version": "2.7.5"
+  "upstream_version": "3.0.1"
 }