What is the correct official way of installing Immich, I tried with help of Ai but no success- I am use the Version 7.3.0-rc.1

same here. official guide for "only officially supported method" uses depreciated docker.compose plugin and very old unraid version. following the steps in the guide (no already existing postgresql and redis) with new "docker compose plus" results in not starting "database" and "immich-server" containers (partial 2/4 stack). I also tried AI solving this but no luck after hours of experimenting.

I also did not find a "complete" CA with no need of configuring other necessary docker containers like postgresql and redis, which is no option for me since i am a beginner in linux.

so atm i am stuck, waiting for a proper guide to get immich to run on my unraid homeserver.

since your post is already a few days old, did you find any help for this?

Edited May 17May 17 by -Sid-

What exactly is the poblem?

You need 3 Dockers: "Immich", Immich-postgres" and "immich-valkey" (and if you want "immich-machine-learning")

Every Docker you find in the "Apps".

As a tip - Run all Docker containers on the same network, e.g., “immich”. (docker network create immich)

The exact problem is an outdated official guide as I already described.

Simply installing the dockers as proposed is not as simple for me unfortunately because it requires filling in a massive amount of details (which I don't have) already during the installation progress. Maybe I (or the AI) will be able to figure the required information out at a later date, but for now I need a proper guide to have a chance using immich.

Oh, sorry, I won't write you a full guide, but I can list the steps you need to take. If anything is unclear, feel free to ask specific questions.

You can find all the Docker images under “Apps”.

1. Create the “immich” network (terminal -> docker network create immich)

2. Install postgresql_immich (Immich_PostgreSQL - ghcr.io/immich-app/postgres:18-vectorchord0.5.3-pgvector0.8.1) and configure the following settings:

Network Type - select “immich”

POSTGRES_PASSWORD - set your own password

Optional

POSTGRES_USER - assign any user (standard is postgres)

POSTGRES_DB - assign any database name (standard is postgres)

PostgreSQL access port - either leave it at 5432 or adjust it (the immich port will always be 5432 anyway)

3. Install Valkey (Immich_Valkey - valkey/valkey:8.0.6-trixie) and configure the following settings

Network Type - select immich

Valkey Port - I don’t even know what the default was here; in my case, it’s definitely set to 6379

VALKEY_PASSWORD - assign your own

4. Install immich (immich - ghcr.io/imagegenius/immich:openvino - i have openvino because i have a intelgpu for machine learning - take the one without or select you gpu brand or just "Default") and configure the following settings

Network Type - Select immich

WebUI - Port 8080 is likely already in use, so assign a different port

DB_HOSTNAME - The Docker name from step two (for example, my Docker container for the database is named “Immich-Datenbank”—I need to enter “Immich-Datenbank” here)

DB_USERNAME - Database name from step two (POSTGRES_USER); if you didn’t assign a name, enter postgres

DB_PASSWORD - The database password you assigned in step two (POSTGRES_PASSWORD)

DB_DATABASE_NAME - the name you assigned in step two (POSTGRES_DB); if you didn’t assign a name, enter “postgres”

REDIS_HOSTNAME - your Unraid IP (192.168.X.X)

DB_PORT - is always 5432 regardless of what you entered in the second step

REDIS_PORT - 6379

REDIS_PASSWORD - your password from step 3 (VALKEY_PASSWORD)

That's it. I didn't go into detail about machine learning, you can set that up once the basic framework is in place.

I also didn't go into all the storage paths for your images or AppData—you can adjust those yourself :)

Edited June 2Jun 2 by Elyeu

What's the difference with the docker from ImageGenius? It's the one I'm running that use immich-postgresql and a redis database (not vaultkey).

I'm not quite sure what you mean, we're both using the ImageGenius image, aren't we?

Valkey is just a fork of Redis by the way.

But if you're setting up a new system, I'd go with Valkey since it's more future-proof than Redis.

Ah, I though it was someone else immich image. Mine is up for the last year if not more and stable so I haven't done anything beside container update. I was using bitnami redis that just broke and just made my own container with the official redis instead (and also created a template).

Is there a gain to go with valkey?

Edited June 3Jun 3 by Nodiaque

21 hours ago, Elyeu said:

Oh, sorry, I won't write you a full guide, but I can list the steps you need to take. If anything is unclear, feel free to ask specific questions.

You can find all the Docker images under “Apps”.

1. Create the “immich” network (terminal -> docker network create immich)

2. Install postgresql_immich (Immich_PostgreSQL - ghcr.io/immich-app/postgres:18-vectorchord0.5.3-pgvector0.8.1) and configure the following settings:

Network Type - select “immich”

POSTGRES_PASSWORD - set your own password

Optional

POSTGRES_USER - assign any user (standard is postgres)

POSTGRES_DB - assign any database name (standard is postgres)

PostgreSQL access port - either leave it at 5432 or adjust it (the immich port will always be 5432 anyway)

3. Install Valkey (Immich_Valkey - valkey/valkey:8.0.6-trixie) and configure the following settings

Network Type - select immich

Valkey Port - I don’t even know what the default was here; in my case, it’s definitely set to 6379

VALKEY_PASSWORD - assign your own

4. Install immich (immich - ghcr.io/imagegenius/immich:openvino - i have openvino because i have a intelgpu for machine learning - take the one without or select you gpu brand or just "Default") and configure the following settings

Network Type - Select immich

WebUI - Port 8080 is likely already in use, so assign a different port

DB_HOSTNAME - The Docker name from step two (for example, my Docker container for the database is named “Immich-Datenbank”—I need to enter “Immich-Datenbank” here)

DB_USERNAME - Database name from step two (POSTGRES_USER); if you didn’t assign a name, enter postgres

DB_PASSWORD - The database password you assigned in step two (POSTGRES_PASSWORD)

DB_DATABASE_NAME - the name you assigned in step two (POSTGRES_DB); if you didn’t assign a name, enter “postgres”

REDIS_HOSTNAME - your Unraid IP (192.168.X.X)

DB_PORT - is always 5432 regardless of what you entered in the second step

REDIS_PORT - 6379

REDIS_PASSWORD - your password from step 3 (VALKEY_PASSWORD)

That's it. I didn't go into detail about machine learning, you can set that up once the basic framework is in place.

I also didn't go into all the storage paths for your images or AppData—you can adjust those yourself :)

Thank you very much! This is a guide because it worked for me! You should hand it out to the people managing the "official guides" on the immich homepage ;)

Hi,

I've a problem with the new version 3.

Immich didn''t work anymore:

1. I switched from Redis to Immich_Valkey

2. I switched from Postgres_SQL from tensorchord/pgvecto-rs:pg16-v0.3.0 to ghcr.io/immich-app/postgres:18-vectorchord0.5.3-pgvector0.8.1

3. After that, Immich started but like it was a new setup

I clicked on "restore from a backup" or something like this (my Immich is in French), load a back-up in version v2.7.5 but

it fails:

Error: /usr/lib/postgresql/18/bin/psql non-zero exit code (3)
and 1 other object (see server log for list)
ERROR:  extension "vectors" is not available
HINT:  The extension must first be installed on the system where PostgreSQL is running.

But I don't know what I have to do.

I tried alternative Postgres_SQL (rorar's Repository, bmartino1's Repository) with same result.

I read on forum that I have to edit an .env file but I don't see where. Do you have an idea ?

Edited July 10Jul 10 by zarkoff

The problem is you never updated your DB. I had the same problem. I myself moved all to Roar instead of having a all in one. Here's what you need to do.

Put back your original postgresql version and restart the database as is. The database should now work. If it doesn't, restore a working database.

Next, your immich container, go back to version 2 using the tag for it. If you were on latest, just use the latest 2 tag available.

Once everything is back working, check the postgres log. You should see at the top a migration for your vector.

Stop postgres and immich

If I recall, all I had to do is migrate to the ghcr.io/immich-app/postgres:18-vectorchord0.5.3-pgvector0.8.1 but the version of the DB you had. Like this is a Postgresql 18, but tensorchord/pgvecto-rs:pg16-v0.3.0 is 16. So, do something like ghcr.io/immich-app/postgres:16-vectorchord0.3.0-pgvector0.3.0 and start. You should see a migration happening. It can be long. Once it's finish, launch Immich. Once immich is in working condition, start a new backup (I simply changed the date of immich daily backup so it would run in the next minute).

Stop both container

Change postgres to ghcr.io/immich-app/postgres:18-vectorchord0.5.3-pgvector0.8.1 and start. It will migrate. Start immich.

Now, if you want to migrate to ROAR like I did, it's very simple. I had to add some --user=99:100 to some of it's container though (else they run on bad user).

For this, what I did is close everything that already exist and install each container one by one. I changed some of the path mapping on the immich container itself to match what I had (this should be easy). I also added a lot of variable that we can't used with the AIO for the configuration (check official immich documentation). Once immich start, I put restore database which restarted immich in maintenance mode. Then, I selected to restore database. Since it was mapped to the exact backup folder from the other immich container, it was able to find it and restore it.

And that's it, you have a immich latest version with official container. This will create 4 new container (immich machine learning, vaulkey, postgres and immich server). If you need hardware acceleration like nvidia, intel or other, select the appropriate immich_Server docker.

Edited July 10Jul 10 by Nodiaque

For anyone that want to migrate to the official container, it's very easy.

This container isn't a bad one, we are many that have used it for a long time and many still use it. This is simply if you want to be on official one where all the documentation from developer apply. Some prefer all in one solution (although it's not that all in one anymore) like this docker, other prefer to have it like it's intended by the author. It's a mater of choice.

I followed Rorar guide (although his guide doesn't use the apps) and official guide with some tweaks.

rorar guide: https://rorar.github.io/immich-unraid-manual/

I didn't do the custom network nor the google migration. Google migration was already done when I installed immich so useless. As for the custom network, I already have a custom network with all my docker. You could create one dedicated to immich, it's up to you if you want to go that route. Just remember, if you are using a reverse proxy where the docker isn't in the same network, you can't use <dockername> directly to refer to it. But you do want a custom network, not Bridge. The reason is with the default Bridge network, you can't use docker name.

The container I used are from Rorar repo:

• immich-vectorchord-db-official : it is the latest supported database ghcr.io/immich-app/postgres:18-vectorchord0.5.3-pgvector0.8.1

• immich_machine_learning_nvenc : Select the one according to your configuration. If using Hardware configuration with NVidia, take this one. Check Rorar docker list and select according to doc

• immich_server_nvenc : Immich server with NVidia HA. Change according to your configuration.

For valkey, I used
immich-valkey : Uses valkey/valkey:latest

There is other valkey, this one is said to be optimized for immich.

For the migration, we will simply create all new container and migrate database.

Preparation

Upgrade postgres to latest supported version. Check previous post for info. You don't have to, but if you have bad vector and such, it make everything way harder since import will fail.

Do a database backup from immich, then shutdown all container regarding immich. If you share redis/vaulkey and postgres, it's ok not to shutdown them but they won't be used anymore.

Rename appdata/immich to something else (immich_bak if you want).

This guide use unraid nobody:users (99:100) configuration. Everthing under appdata for immich and all files in array/pool read/write by immich containers need to be chmod to these with proper permission. If you use custom permission, change accordingly.

Array and share configuration

One thing to keep in mind is how your library, thumbnail and such are configured in your current Immich. With the immich container from this thread, everything is under /photos. Because of that, it's harder to make path separation. Rorar explain well what you should put on SSD and what to put on Array.

On my own configuration (you don't have to follow that), I have 2 share, one call Immich and the other Immich_Cache (that's because I have many SSD used as cache). Immich share is SSD move to Array and Immich_Cache is Array to SSD. Both create new file on SSD. Immich_Cache is just like appdata but on a separate pool.

The reason is for performance, you want to have thumbnail, encoded-video and profile always on a SSD. The rest, you want them on an array since it's the actual file. This make browsing much faster (specially if you configured using multiple size thumbnail instead of original when browsing). It's a bit like Rorar did in his guide at Step 1: Create Unraid Shares - Immich on Unraid — Performance Setup Guide

So for that, it would require to change some path. I myself moved the content from /photos/encoded-video, /photos/thumbnail and /photos/profile to the new SSD share I created. This is a breaking change from this container. I you want to come back to this container, you have to move back those file. You could also just leave it like that.

Recommandation

DO READ EACH DOCKER INFORMATION. Nearly all docker will have extra configuration and explanation in them, like if they are on SSD or not. This migration guide doesn't cover those scenario since they are properly explained in each docker template from Community Apps in Unraid.

1) Start by creating the postgresql server from the apps.

In Extra-Parameters, add

--user=99:100

Input the same password you used for the current Postgresql Immich Database.

If you used a different username then postgres for the old database, the restore function won't work. If you change the username here, it won't work (I already opened a ticket on that). For that, see FAQ chapter later on how to fix the backup.

Change the network to your custom docker network.

Change TimeZone.

Start the container

2) Create Valkey container from the apps

In Extra-Parameters, add

--user=99:100

Change the network to custom docker network

Change TimeZone

Start the container

3) Create machine learning from the apps

Don't forget to take the one with the hardware acceleration you want.

In Extra-Parameters, add

--user=99:100

Change network to custom docker network

change TimeZone

Start the container

This docker have a appdata/immich/model-cache path. Nothing else will write in immich appdata, the official docker doesn't use appdata.

4) Create immich_server from apps

Don't forget to take the one with the hardware acceleration you want.

In Extra-Parameters, add

--user=99:100

Change network to custom docker network

change TimeZone

From here, you have to fill many path. You must point to the path of the already created files from the old immich container. You can select new path but move the content before starting the container. Do read the template, it is quite easy to understand. There is some entry that are information only, like "--- HDD Storage (Array) ---". Rorar use that to separate each type of path/variable in section to make it easier to read.

So in short, in the old template, we had everything mapped to /photos. The official one use a per asset mapping. You can easily just map each one to them.

Exemple on mine, everything was under /mnt/user/immich/photos/ in the old template. This is a Share that use cache for new file then move to Array. With this new docker, I've simply link directly each subfolder.

I did the samething with the SSD variables. But the difference is I have another share with New file created to SSD and mover move from Array to SSD. I do have a pool dedicated for that.

Under Database

DB_HOSTNAME: immich-vectorchord-db-official (unless you changed the container name)

DB_PORT: 5432 (unless you changed it)

DB_USERNAME: postgres

DB_PASSWORD: you_postgres_password

DB_DATABASE_NAME: immich

Under Valkey:

REDIS_HOSTNAME: immich-valkey (unless you changed it)

Change TimeZone.

I changed the UMASK to 000 cause that's how I like it (personal preference).

If you have any other custom path, map them accordingly.

Start the container

5) Migrating the database

Now that everything is mapped, you should see in the log that it's finding multiple things. Reach the WebUI. You should be greated with a setup screen. Press restore from backup. This will restart immich in maintenance mode (you might need to refresh the page). If refreshing the page lock you out, check the immich docker log. You will see a link that you open and get you directly in immich maintenance mode.

Once in maintenance mode, it will scan everything and have green check. Inspect that everything is good. The only thing I have an error was profile because I have nothing in it. It must be green. Click next and select the most recent backup. And then it will import. If it fail, you need to read the error and find the problem. I myself had trouble because I didn't migrate to latest database version and removed the old vector. Go read previous post for guidance.

Once it's finish, enjoy!

If you have a reverse proxy, you will need to reconfigure because the official container use port 2283 instead of 8081.

6) Container start/stop order

Since we are not all in one anymore, we have an order to start and stop to prevent issue. It won't be a big deal since the service is pretty resilient, but it's still a best practice. The stop order is simply the start in reverse. The start order you want to have in the docker list (and if you use backup solution like appdata-backup-restore, create a group and order them)

1) immich-valkey

2) immich-vectorchord-db-official

3) immich-machine-learning

4) immich-server

FAQ

Q. I'm using another user then postgres in postgres database

A. You must migrate to postgres. There's other way, but you will be in unsuported teritory. The easiest way I found is to take the immich database backup on a computer, unzip and open the .sql file in something like notepad++.

Search for the old database username. For instance, mine was immich. You should find entry like:

Owner: immich

OWNER TO immich;

So the idea is simple. Do a find and replace. I suggest not looking only for the name cause, if like me you used immich, you will rename stuff that you don't want. So for exemple, I did a find and replace all with

find: Owner: immich

Replace: Owner: postgres

Then

find: OWNER TO immich;

Replace: OWNER TO postgres;

Save the file

Now, at the restore database, choose upload. Once the upload is finish, find it in the webgui and restore.

Edited July 10Jul 10 by Nodiaque

12 hours ago, Nodiaque said:

The problem is you never updated your DB. I had the same problem. I myself moved all to Roar instead of having a all in one. Here's what you need to do.

Put back your original postgresql version and restart the database as is. The database should now work. If it doesn't, restore a working database.

Next, your immich container, go back to version 2 using the tag for it. If you were on latest, just use the latest 2 tag available.

Once everything is back working, check the postgres log. You should see at the top a migration for your vector.

Stop postgres and immich

If I recall, all I had to do is migrate to the ghcr.io/immich-app/postgres:18-vectorchord0.5.3-pgvector0.8.1 but the version of the DB you had. Like this is a Postgresql 18, but tensorchord/pgvecto-rs:pg16-v0.3.0 is 16. So, do something like ghcr.io/immich-app/postgres:16-vectorchord0.3.0-pgvector0.3.0 and start. You should see a migration happening. It can be long. Once it's finish, launch Immich. Once immich is in working condition, start a new backup (I simply changed the date of immich daily backup so it would run in the next minute).

Stop both container

Change postgres to ghcr.io/immich-app/postgres:18-vectorchord0.5.3-pgvector0.8.1 and start. It will migrate. Start immich.

Now, if you want to migrate to ROAR like I did, it's very simple. I had to add some --user=99:100 to some of it's container though (else they run on bad user).

For this, what I did is close everything that already exist and install each container one by one. I changed some of the path mapping on the immich container itself to match what I had (this should be easy). I also added a lot of variable that we can't used with the AIO for the configuration (check official immich documentation). Once immich start, I put restore database which restarted immich in maintenance mode. Then, I selected to restore database. Since it was mapped to the exact backup folder from the other immich container, it was able to find it and restore it.

And that's it, you have a immich latest version with official container. This will create 4 new container (immich machine learning, vaulkey, postgres and immich server). If you need hardware acceleration like nvidia, intel or other, select the appropriate immich_Server docker.

@Nodiaque Thank you for your help.

I could restore version 2.7.5 and get it working again, but migration is problematic. Attempting to upgrade from tensorchord/pgvecto-rs:pg16-v0.3.0 to ghcr.io/immich-app/postgres:16-vectorchord0.5.3-pgvector0.8.1 breaks my installation: Postgres logs show errors, and Immich enters an infinite loop, as if the upgrade never triggers.

Since every upgrade attempt fails, I’ve decided to create a fresh instance and restore from my backups. My Share and Backup files are intact, so I’m confident this will work—I just need time to follow your guide and set it up properly.

Edited July 11Jul 11 by zarkoff

You are going to high version that's why. Check on my post, I said to go at postgres 16 but vectorchord 0.3.

ghcr.io/immich-app/postgres:16-vectorchord0.3.0-pgvector0.3.0

Im unsure if this is the right tag, if it says not found, go at the repo url and find the tag nearest to that version. Once this is done, then you go at latest version.

You won't be able to restore a backup with latest database version even with my guide. It will fail at vector. You need to migrate the database.

Restore database at your old version and check the log, there will be a link for the migration and from what I recall, they put the right version to go for the migration of the database. Pretty sure it's what I wrote but I could be off.

Edited July 11Jul 11 by Nodiaque

@Nodiaque

Ok but in Immich log, I see:

[Nest] 613  - 07/11/2026, 3:57:47 PM     LOG [Api:WebsocketRepository] Initialized websocket server
/app/immich/server/dist/services/database.service.js:93
                throw new Error(messages.invalidDowngrade({ name, extension, availableVersion, installedVersion }));
                      ^

Error: The database currently has VectorChord 0.5.3 activated, but the Postgres instance only has 0.3.0 available.
    This most likely means the extension was downgraded.
    If VectorChord 0.5.3 is compatible with Immich, please ensure the Postgres instance has this available.
    at /app/immich/server/dist/services/database.service.js:93:23
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async /app/immich/server/dist/repositories/database.repository.js:392:27
    at async /app/immich/server/node_modules/.pnpm/[email protected]/node_modules/kysely/dist/cjs/kysely.js:541:20
    at async DefaultConnectionProvider.provideConnection (/app/immich/server/node_modules/.pnpm/[email protected]/node_modules/kysely/dist/cjs/driver/default-connection-provider.js:12:20)
    at async /app/immich/server/dist/repositories/database.repository.js:389:13

So 0.5.3 should work no ?

But if I use the version : ghcr.io/immich-app/postgres:16-vectorchord0.5.3-pgvector0.8.1

Then the Immich log says (still version 2.7.5):

[Nest] 531  - 07/11/2026, 4:12:47 PM    WARN [Api:DatabaseService] Could not run vector reindexing checks. If the extension was updated, please restart the Postgres instance. If you are upgrading directly from a version below 1.107.2, please upgrade to 1.107.2 first.
node:internal/process/promises:394
    triggerUncaughtException(err, true /* fromPromise */);
    ^

PostgresError: could not access file "$libdir/vectors": No such file or directory
    at ErrorResponse (file:///app/immich/server/node_modules/.pnpm/[email protected]/node_modules/postgres/src/connection.js:815:30)
    at handle (file:///app/immich/server/node_modules/.pnpm/[email protected]/node_modules/postgres/src/connection.js:489:6)
    at Socket.data (file:///app/immich/server/node_modules/.pnpm/[email protected]/node_modules/postgres/src/connection.js:324:9)
    at Socket.emit (node:events:508:28)
    at addChunk (node:internal/streams/readable:563:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:514:3)
    at Readable.push (node:internal/streams/readable:394:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23) {
  severity_local: 'ERROR',
  severity: 'ERROR',
  code: '58P01',
  file: 'dfmgr.c',
  line: '208',
  routine: 'internal_load_library'
}

So I don't know what to do...*

---

Edit: I think I find the way to do it (I keep previous message to understand to what error the below fix is referring to).
in Postgres container:

1. keep the tensorchord/pgvecto-rs:pg16-v0.3.0,

2. in container console, type
psql -U immich -d immich -c "DROP EXTENSION IF EXISTS vectors CASCADE;" (Note: If you changed the default database user or database name from "immich", update the -U and -d flags accordingly).

3. Update with new ghcr.io/immich-app/postgres:16-vectorchord0.5.3-pgvector0.8.1

4. Run Immich it should be ok.

Original post:

Hope it helps.

Edited July 11Jul 11 by zarkoff

I had yourbpriblem. What happened is your Bd was upgraded but failed.

Restore from a working backup of the original version before all of this. Then start the upgrade step.

For the exact container, follow the guide the log will output.

Because you used postgres 18 at one time, it updated and you are now in a stuck place.

I'm away so I didn't read everything, sorry. But the beginning of your post show me exactly what happened to me. I did like you did, used a too high version and it failed the upgrade.

Restore old postgres 16 with vector, boot up immich 2.7.5 with it. When it's working, start the upgrade from postgres 16 with same version of pgvector (the guide will show you).

Once this is done, then you can migrate to postgres 18 and upgrade vector

Edit: I see you might have found a way to fix the database. If it's not working, you can try what I wrote. That's how I fixed mine after doing the same mistake.

Edited July 11Jul 11 by Nodiaque

On 5/17/2026 at 5:30 AM, -Sid- said:

... uses depreciated docker.compose plugin and very old unraid version.

Are you aware that there is a new Docker Compose plug-in called Docker Compose Plus that is a drop in replacement? And works perfectly with Immich's official install guide?

I know, I'm running it, and have been for a while with zero problems to include the recent update to Immich 3.0.2 and unraid 7.3.2; and I've been updating every step of the way since at least version 2.5x of Immich and whatever version of Unraid was around that same time (Jan?)

I myself knows it but I hate it. I prefer having container that do stuff the unraid way.

4 hours ago, Nodiaque said:

Edit: I see you might have found a way to fix the database. If it's not working, you can try what I wrote. That's how I fixed mine after doing the same mistake.

Yes, it has fixed my problem. (the: psql -U immich -d immich -c "DROP EXTENSION IF EXISTS vectors CASCADE;" in Console).

A big thank you for your help, it help me to understand the problem and then find the solution.

I see you seems to have a user immich for the database? Check your log, postgres was giving me error when I migrate to the latest version. At immich, they recommended to migrate to postgres user

On 7/12/2026 at 1:54 AM, Nodiaque said:

I see you seems to have a user immich for the database? Check your log, postgres was giving me error when I migrate to the latest version. At immich, they recommended to migrate to postgres user

Well yes, you're right I need to check how to add a user in postgres... I don't know the syntax or command line.

1 minute ago, zarkoff said:

Well yes, you're right I need to check how to add a user in postgres... I don't know the syntax or command line.

I made a guide on previous post that can help you migrate to postgres user instead of immich.

Hello, hopefully this is the right area of the forum to ask, I am running Immich container v1.143.1 and need to update to v3.0.3.

Currently its setup using Immich container (ghcr.io/imagegenius/immich), and using the PostgreSQL (tensorchord/pgvecto-rs:pg16-v0.3.0)

Is there a guide I can follow to safely upgrade? Thanks!

Yes, read previous post, I posted a guide to migrate to the official docker but there's also in it a guide to migrate database that you can follow and continue using this container

As for the postgresql migrationg, simply follow what's in the log file of the container (restart it and look at the beginning, there's a link to a guide).

Edited 36 minutes ago36 min by Nodiaque