Custom locations not respected
I'm trying to separate where immich uploads photos from the rest of the data needed to run the application, thus I've followed the instructions https://immich.app/docs/guides/custom-locations/. The problem is when I start my docker container it seems to ignore the custom locations, recreates all the subdirectories where
UPLOAD_LOCATION
is specified, then errors because it can't find one of the .immich
files:
12 Replies
:wave: Hey @PickleRick,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. 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 ps -a
docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: 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)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l
and df -h
).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close
command, and re-open it later if needed.env file:
docker-compose
"immich" is the name of the user the containers are executing under
if we go look at the "upload" location, you can see folders and .immich files missing, which would generate the error. But it shouldn't matter if it's actually following the configuration
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
It does matter because you need to move the old folders to the new location
Immich realizes that files are missing
sorry, what matters?
You said "it shouldnt matter if its following the config"
so immich needs the directory structure in two locations, even with custom locations?
The config would expect a file at /pool1/photos/immich/library/.immich , which is missing
No, it just needs it in the place you mapped it to
Oh, the empty directories are a docker thing, not immich
When you make nested bind mounts there will be an empty folder in the source
i think i see the issue, it's actually compllaining about a file that's supposed to be there, even if it is using the custom mounts. it's complaining about where the upload folder should be, derp.
I guess I got distracted by the empty directories being created
alright, this still isn't working
Library does not go in upload
I gave the path above
alright, looks like i've got it solved
i didn't RTFM hard enough
thanks for the help
This thread has been closed. To re-open, use the button below.