External Library guidance (yes another one)

I'm running Immich in a docker container on a Synology DS723+ and it's been up and running for a few months now. It's pretty much digested everything I've thrown at it and it's backing up photos from my android phone just fine. My NAS is set up w/ volume1/docker/immich, but I'd like to add the external library volume1/photo and I can't seem to accomplish this. I use portainer and what I thought to be the path: volumes: - /volume1/docker/immich/upload:/usr/src/app/upload:rw - /volume1/photo:/volume1/photo:ro # < this is what I added When I added "/volume1/photo" as the import path in the External Library Management section of the program I was pleased not to see the Warning this time. I went to scan the new external library and nothing happed. Zero assets rather than the 10K I expected. Clearly I am out of my depth here. Thanks for any guidance.
18 Replies
Immich
Immich6mo ago
:wave: Hey @Screwball, Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich :immich:. References - Container Logs: docker compose logs docs - Container Status: docker compose ps docs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy Checklist 1. :ballot_box_with_check: I have verified I'm on the latest release(note that mobile app releases may take some time). 2. :ballot_box_with_check: I have read applicable release notes. 3. :ballot_box_with_check: I have reviewed the FAQs for known issues. 4. :ballot_box_with_check: I have reviewed Github for known issues. 5. :ballot_box_with_check: I have tried accessing Immich via local ip (without a custom reverse proxy). 6. :ballot_box_with_check: I have uploaded the relevant logs, docker compose, and .env files, making sure to use code formatting. 7. :ballot_box_with_check: I have tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable (an item can be marked as "complete" by reacting with the appropriate number) If this ticket can be closed you can use the /close command, and re-open it later if needed. Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
Zeus
Zeus6mo ago
So you have checked off the boxes but you haven't posted anything the bot asked for you shold post the compose, env, screenshots of all that you added, and all container logs also the output of the following commands on the host:
ls /volume1/photo
docker exec -it immich_server ls /volume1/photo
docker inspect immich_server
ls /volume1/photo
docker exec -it immich_server ls /volume1/photo
docker inspect immich_server
You may have to adjust some of those for portainer, not sure
Screwball
ScrewballOP6mo ago
This would be my stack from portainer. As I mentioned in the previous entry, everything else worked fine so I didn't think I needed to waste bandwith by adding a buch of screen shots of things working OK.
Screwball
ScrewballOP6mo ago
Please advise if there's something else missing. Thanks.
Screwball
ScrewballOP6mo ago
This is where I have a problem. I can copy and past and have successfully done so in portainer, but that's it. What has a few commands I haven't seen, specifically 'exec' or 'inspect' and that may be the difference when using portainer.
schuhbacca
schuhbacca6mo ago
It says in the log permission is denied to read the assets.
Screwball
ScrewballOP6mo ago
Probably why it would have been a good idea to post it in the 1st place. Not sure why it would be denied and it's only the 1st of several folders in that dir. I looks like it quit after the first one.
Zeus
Zeus6mo ago
It goes In alphabetical order so that makes perfect sense They’re probably all incorrect
Screwball
ScrewballOP6mo ago
From what I understood I point it to a folder and it would sweep the images in that and subordinate folders as well. I will try pointing it to only a folder that contains image files and see if I get an error there.
Zeus
Zeus6mo ago
no, you will get the same error.. you need to fix the permissions on your filesystem
Screwball
ScrewballOP6mo ago
OK, that makes sense. Is that because it's containerized? So more of a docker issue than an Immich issue.
Zeus
Zeus6mo ago
This is more of an underlying filesystem /mount point issue , or possibly docker. Not immich, no
Tempest
Tempest6mo ago
Are you sure that there are any pictures in that location? Can you navigate to it via the CLI and type something like ls to see the photos? Generally Synology photos are stored under a different file structure
Screwball
ScrewballOP6mo ago
Yes, I'm sure there are images in the folder. I can navigate to it with several different options and the error I get is a permission denied of a sub folder so it's reading the location enough to report permission denied.
Zeus
Zeus6mo ago
You need to fix your host or network permissions to allow immich to view all the files and folders
Screwball
ScrewballOP6mo ago
Yeah, that's the rub. I've set the permission for the /volume1/photo to Everyone. I use portainer and found out how to check the permision and can't seem to give it what it wants. It seems to show the 'ro' tag is there. I figured there'd be someone running immich on a syno that tried an external library, but I haven't found one yet.
No description
Tempest
Tempest6mo ago
Several different options? So you've done it from the command line?
Screwball
ScrewballOP6mo ago
I've accessed via Win cmd line, Win as a mounted drive with File Explorer, in syno using the native file station, syno Photos, or any other syno app. The one common issue is I can't seem to access anything outside of a docker container that's why I figured it was a container related permission issue. I may have found something. Checking now. I checked the folder for photo and checked the permission for that folder. Virtually everyone has either rw or ro permission, however, if I check a sub folder my permission options change and none are selected and I cannot change them. So I have a couple of usb drives pluged into the NAS and could configure permissions there, created a test folder and gave it the appropriate permisison. I reconfigured Immich to look at that drive and got it to recognize my test image. So that's progress, but it's going to take me a bit to figure out how to digest all of this. I'll probably be able to resume poking at it on Friday.

Did you find this page helpful?