"Failed to write upload/encoded-video/.immich" - permissions seem to be ok
I'm trying to migrate from a systemctl + external mount setup to a Kubernetes + NFS setup. Immich fails to start at read/write/create check of the upload dir.
Based on the following, I think permissions should be ok.
and the above setup still fails with
I did not copy the uid:gid for
/usr/src/app/upload/encoded-video/.immich, but it's 1000:1000 too.
I already checked the linked docs, but could not figure out my issue. Does anyone have any pointers?4 Replies
:wave: Hey @nagyviktor,
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:What is in the folders, just in case,
find /usr/src/app/upload -maxdepth 2 -ls
Can you touch .immich from inside the container?
(NFS permissions regularly appear here on Discord)Touch failed 🙀
But why?! (I removed a few "redundant" lines to be allowed to post)
I found the issue. It was a combination of my NFS export config and the previously created PersistentVolume (obviously) not picking up an NFS configuration change, when I fixed my NFS config. Basically, I forget to remove/recreate the PV when I fixed the NFS export.
As I recreated the PV, the pod could start.
Oh huh 🫣
Cool you resolved it