Closed krayakin closed 9 months ago
[...] must be mounted in both the main and microservices pods
I came to the same conclusion. I defined an additional NFS mount and was able to run the import. However, metadata extraction and thumbnail generation fail. Microservices logs show output such as
exifData parsing failed due to Error: File not found - /mnt/photos/IMG_20191217_213933.jpg for asset 2f93ebe4-775d-475c-8c91-ff4e772f2671 at /mnt/photos/IMG_20191217_213933.jpg
Unable to run job handler: Error: Input file is missing: /mnt/photos/IMG_20191217_213933.jpg
I defined an additional NFS mount and was able to run the import.
I can't even get the import to run. It tells me right away it can't find the path. I'm assuming it's the microservices pod that is complaining about this.
Also trying to use this feature and face the same problem. Is there any way to change the Chart to mount an Additional folder to the main pod and microservices pod?
Guys we have a Discord to discuss this, once a bug is reported unless it's code we keep discussions there, locking this up but feel free to +1 / thumbs up the original post, someone will get around to it or if someone wants they can file a PR.
App Name
Immich
SCALE Version
22.02.3
App Version
1.65.0_7.1.3
Application Events
Application Logs
Application Configuration
Describe the bug
Unable to use Immich External Path to a mounted additional storage.
In order for the storage to be used properly by Immich it must be mounted in both the main and microservices pods.
To Reproduce
immich upload --key xxxxxxx --server https://photos.local/api <additional_storage_mount> --recursive --import
Expected Behavior
Folder is scanned and imported into library
Screenshots
N/A
Additional Context
According to documentation for this feature the path needs to be accessible in both main and microservices pods https://documentation.immich.app/docs/features/read-only-gallery#register-the-path-for-the-user
I've read and agree with the following