chown error on docker start
Hello! New here, trying to get photos into a solution other than SmugMug for long-term storage and viewing.
I've configured a VM (running on proxmox) with ubuntu. Installed docker; running an Immich container. I was able to get external libraries working fine referencing an NFS mount via the .env variable. Now I'm trying to get the default upload location to also sit on an NFS mount, as the VM doesn't have more than 80gb available rn (which I plan to fill with thumbnails).
I get the mount working via this fstab entry:
192.168.1.158:/var/nfs/shared/media/photo /mnt/nas_photo nfs auto,nofail,noatime,nolock,intr,tcp,actimeo=1800 0 0
Mounts fine and I can move files there, create directories, all working as expected.
I then set the following in .env:
My docker compose has this for immich-server:
When starting docker, I get this error:
Error response from daemon: error while creating mount source path '/mnt/nas_photo/upload': chown /mnt/nas_photo/upload: operation not permitted
The upload folder is created on container start:
drwxrwx--- 1 977 988 0 Nov 2 12:25 upload
I'm not sure where to go from here. My understanding is that docker (by default) will run as root and should have access to the whole folder structure under /mnt/nas_photo.9 Replies
:wave: Hey @Charlie Beals,
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.Output from
mount
Output from df -h
192.168.1.158:/var/nfs/shared/media/photo 17T 4.5T 12T 27% /mnt/nas_photoSuccessfully submitted, a tag has been added to inform contributors. :white_check_mark:
Output of
docker stats after starting the container:
The actual output from running docker compose up -d
This is an issue with your NFS mount not giving permissions for root user to write to the mount
@Zeus is that generally an issue with the fstab entry? Or would it be on the NAS host side?
Either really. Not immich 😛
Probably the NAS
The reason I opened the ticket was because I can mount the drive and read/write to it fine from the VM. It's only the immich container that struggles to access the mounted directory.
That being said....I just shut down and restarted the container (without making any changes) and didn't get an error. Now Immich can read/write to that location. 🤷♂️ I replicated the issue about 6 times, so it's definitely repeatable. And resolved by simply shutting down and restarting the Immich container.
This thread has been closed. To re-open, use the button below.