Closed niko86 closed 3 months ago
Is /mnt/prox-share/docker/makemkv/config
mounted with a specific user/group id ? Looks like the container doesn't have permission to write to it. Note that by default, the container runs with user/group ID 1000/1000. This can be changed via USER_ID
and GROUP_ID
environment variables if needed.
Thank you for the response. I’m very much an amateur when using Linux but I checked the user I’m running portainer under and it’s uid and gid are both 1000.
I got things working using a config and user location in a docker volume. But I couldn’t locate the SMB share for ripping to so was obviously still a permissions problem.
TRUENAS which is serving the share has the SMB user setup with suitable permissions, but no SUDO ability. I can confirm the docker images can write folders and some files like a .conf (forget the name as I’m not at my PC, not in the log as it has been generated on a previous boot of the container). So I assume your docker container requires the ability to make some files with SUDO? I’ll try adding SUDO permission in TRUENAS as well.
I can confirm the docker images can write folders and some files like a .conf
How did you test that ? Writing as root from the container might work, but not from user 1000/1000.
So I assume your docker container requires the ability to make some files with SUDO?
sudo is not needed. The problems seems that writing as user 1000/1000 is not allowed by the SMB mount on truenas. Usually, when you mount a share on linux, you have the ability to specify the associated user/group id. For example, see https://serverfault.com/a/49238.
How did you test that ? Writing as root from the container might work, but not from user 1000/1000.
It worked just with the default 1000/1000, which is why I was surprised it failed on the services. I'm finding Linux permissions are a very steep learning curve! In TrueNAS the user and group ids are 3000/3000, videos on YouTube show others with 1000/1000 so definitely is something i have configured incorrectly. I will read over that article this evening, thank you for your help.
Ok got to the bottom of the issue, my mistake in setting the share in fstab, i used the UID and GID from TRUENAS e.g. 3000/3000 rather than the local user UID and GID of 1000/1000. Once it was changed its all working.
So not a bug in the container, but hopefully my mistake might help someone else.
A huge thank you jlesage for the guidance in the right direction and this great container :)
Current Behavior
The docker container (running on portainer) seems to fail on a permission error on xdg and nginx, the storage is a smb share which I believe is now properly setup in the host linux OS.
EDIT: Initially the container startup failed due to [cont-init ] 55-makemkv.sh: ln: /config/.MakeMKV: Not supported i fixed this by adding "mfsymlinks" to my systems fstab.
Container creation
Container log