Updated unraid CA docker container to 1.137.1, can't solve inconsistent media location
Hello! It's my first time here, so I'll try and get all of the necessary data down. I'm making this post at my wits end, and will be finally giving up for the night after I make it, so if more info is needed from me I'll check back on this tomorrow.
My unraid docker-based setup has been working great for a while, before the update I was on 1.135.3. I remember seeing the breaking change about absolute file paths in 1.136.0, so I didn't update, but I forgot about that today and decided to update, since I was more than a version behind.
I have my immich container, a redis container, and a postgreSQL container, all on their own VLAN within the docker system.
The error I'm getting is the first attached image. The thing is, I have my file paths set to absolute? (second attachment). I tried reinstalling both the database and the immich containers, I tried changing the paths to relative and then back to absolute (which does change the error I get, it throws an "unable to find /photos/encoded-video/.immich",) so I think it's able to connect to the /photos database, it just doesn't like it? I couldn't find anyone else online with this exact issue, so I decided to come here.
I don't have a compose.yaml, nor a .env file (at least not visibly), so I'm not sure what exactly to provide past the two screenshots. My 3 containers are set up to talk to each other, and have had no trouble doing so in the past, so I'm fairly certain that isn't the problem.
I need to go to bed, and this is really not what I was planning on doing with my entire evening, so any help would be greatly appreciated. I know 1.137.1 launched only a couple days ago, so if the solution to my problems is to simply wait for a new minor version, that will probably be fine.
5 Replies
:wave: Hey @TheSockCollector,
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.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:They're going to fix it in the next patch
This thread has been closed. To re-open, use the button below.