I use both truenas and immich, but… i did not deploy immich using the truenas apps.
instead… i did it via dockge (installed via truenas apps), docker compose.
so, i can’t do the postgress update like u guys….
i checked around and this was what immich said
alextran1502
2 weeks ago
MaintainerWe are planning to have a proper migration to pg18 soon. So it’s better to wait until then
So i am waiting.
Right now i am using the docker compose that is the latest on immich, and that uses the OLDER posgres.
I did try to delete the older posgress folder after first stopping the container, then change posgress database to v18 vector, but that didn’t work. So i will have to wait for that update the maintainer mentioned.
I think there may be a way to do it, but from what AI said, you had to start the posgres in a temporary location to avoid it from not running due to error, so that you can run the command (the possible fix), then moving it back to start fully. But that is just way more than i can do, so i’ll just wait.
Last resort is just sticking to the truenas app install method.
So if you are in a similar situation, just wait. the update for this from immich side is coming soon. So hopefully that means they will update immich and the docker compose (which includes the posgress v18) and it will just run without issue. At the very least you may have to delete the posgres database and start from scratch, but i am ok with that as long as it runs.
*update
this is the posgres v18 with the pgvector, this is the one i tried to use but immich current version wouldn’t accept as is
http://ghcr.io/immich-app/postgres:18-vectorchord0.5.3-pgvector0.8.1
As for the possible fix i mentioned, i was referring to this specifically. I don’t know if it would actually work or not, but it was a lead
But the problem why i couldn’t do that, was because i use docker compose which has immich, posgres all loaded up in the same docker compose. so posgres would fail to start up… so… i could not run the commands with that possible fix.
asking ai, they mentioned u had to run that thing in a temporary space to get around a container not running due to error. that’s as far i got. Didn’t want to do stuff i’m not too certain about to avoid creating issues. hence why i am waiting ^^;