Open Ogglord opened 2 months ago
Hello, the guide is out-of-date. IIRC, immich uses absolute paths now, adding a new volume mapped to /app/immich/server/upload
should work. You can check what kind of paths are stored in the database to make sure what should be the appropriate volume mapping.
Okay, thanks for the info. It makes more sense.
I tried mapping the full path to /app/immich/server/upload but it didnt work still. The logs complain and says that a relative path wasnt found e.g. "ENOENT file not found: 'upload/thumbs/<guuid>/xx/yy.thumb.jpg'"
Do you know which table I should look at? the few paths I found looked relative, i.e. they didnt start with a slash `'/'.
This is an example from the assets
table
It's a bit sad that this monolithic build isnt 100% compatible with original docker build
It's a bit sad that this monolithic build isnt 100% compatible with original docker build
We made some deployment choices to make maintenance easier. We should update the migration guide, it should be straightforward and I don't understand why it does not work with your setup.
@Ogglord Hey, I just wanted to check whether you have found a solution to your problem? I've been struggling here for a few hours with the same issue and just can't find a solution.
I am running Unraid and I am trying to migrate from the official docker after importing my photos to that instance.
I have tried to follow the guide here with no effect. I have also tried to map the volumes to
/photos
and/usr/src/app/upload
and even/app/immich/server/upload
since that is where immich seems to be looking.Setting the env variable
IMMICH_MEDIA_LOCATION=/photos
have no effect. No matter what I try immich still searches in/app/immich/server/upload/...
. The only explanation I can imagine is that a relative path in the Postgres database that is combined with the working directory of the immich executable...