Can't Create New Immich Instance Postgres Upgrade

Apps and Virtualization
1

I had an existing instance of Immich. It bombed out in the great Postgres 15 to 18 debacle of 2026. It’s been all these months and I finally am ready to just wipe and start over.

I created brand new datasets that have no data in them, and removed the postgres folders from my old datasets, so all I have left is media uploads.

When trying to spin up my new instance, it fails and tells me to look at app_lifecycle.log. In there, I have

[2026/07/25 15:56:49] (ERROR) app_lifecycle.compose_action():58 - Failed 'up' action for 'immich' app:  Network ix-internal-immich-immich-net  Creating
Network ix-internal-immich-immich-net  Created\n Container ix-immich-permissions-1  Creating
Container ix-immich-permissions-1  Created
Container ix-immich-machine-learning-1  Creating
Container ix-immich-redis-1  Creating
Container ix-immich-pgvecto_upgrade-1  Creating
Container ix-immich-redis-1  Created
Container ix-immich-pgvecto_upgrade-1  Created
Container ix-immich-pgvecto-1  Creating
Container ix-immich-machine-learning-1  Created
Container ix-immich-pgvecto-1  Created
Container ix-immich-server-1  Creating
Container ix-immich-server-1  Created
Container ix-immich-permissions-1  Starting
Container ix-immich-permissions-1  Started
Container ix-immich-permissions-1  Waiting
Container ix-immich-permissions-1  Waiting
Container ix-immich-permissions-1  Waiting
Container ix-immich-permissions-1  Exited
Container ix-immich-redis-1  Starting
Container ix-immich-permissions-1  Exited
Container ix-immich-pgvecto_upgrade-1  Starting
Container ix-immich-permissions-1  Exited
Container ix-immich-machine-learning-1  Starting
Container ix-immich-redis-1  Started
Container ix-immich-pgvecto_upgrade-1  Started
Container ix-immich-pgvecto_upgrade-1  Waiting
Container ix-immich-permissions-1  Waiting
Container ix-immich-machine-learning-1  Started
Container ix-immich-permissions-1  Exited
Container ix-immich-pgvecto_upgrade-1  service "pgvecto_upgrade" didn't complete successfully: exit 1
service "pgvecto_upgrade" didn't complete successfully: exit 1

So what’s happening? How does it fail to upgrade something that needs no upgrading? I can’t recall, but I did modify manifests when troubleshooting my other instance, but I recall them being in folders by version, and since this is a new version, there shouldn’t be any bleed over.

2

Postgres runs as uid 999, which in truenas is the build in netdata user. Did you give permissions on the dataset you want to use to that user?

3

I did not change any permissions, the app config defaults to user id and group id 568, not 999. I looked at my old dataset and I have no special permissions set there, just 0744 with owner root, group root.

EDIT: FIXED now. That did seem to be the issue. I noticed the app has an Automatic Permissions checkbox where it would chown the dataset if it could not access it. It didn’t change the upload data, just the postgres-data dataset, changing the owner to netdata and group to docker.

4

As mentioned the postgres side container needs permissions for uid which is also shown in the run as context in the truenas apps store

image
image417×572 8.9 KB