Xinv9 0 Posted February 9, 2022 Share Posted February 9, 2022 I'm struggling with the write permissions for my Emby server. It runs fine, except for the write permissions: nfo, srt, pictures are not saved after a refresh and an error is reported in the logs (attached) immediately after I try that. The strangest thing is that I did succeed in getting delete permissions: I can delete videos from Emby. I've already checked File Permissions Guide for New Linux Users. And read multiple posts of people having similar problems, but that didn't help me so far. I'm running Emby in a docker, the docker-compose is run from uid:1000: version: "2.3" services: emby: image: emby/embyserver container_name: embyserver volumes: - /home/snip/emby:/config # Configuration directory - /mnt/nas_video:/mnt/video # Media directory ports: - 8096:8096 # HTTP port - 8920:8920 # HTTPS port devices: - /dev/dri:/dev/dri # VAAPI/NVDEC/NVENC render nodes restart: unless-stopped etc/fstab: //192.168.1.16/video /mnt/nas_video cifs user=###,pass=###,vers=3.0,auto,noperm 0 0 Without the noperm only root had write access, so I figured this would help. If I go into the mount with uid 1000 I have write access, but it didn't give me write access for Emby. The mount is to a file share on Synology. The user that has the mount, has write access for the shared folder. embyserver.txt Link to comment Share on other sites More sharing options...
Abobader 2952 Posted February 9, 2022 Share Posted February 9, 2022 Hello Xinv9, ** This is an auto reply ** Please wait for someone from staff support or our members to reply to you. It's recommended to provide more info, as it explain in this thread: Thank you. Emby Team Link to comment Share on other sites More sharing options...
Xinv9 0 Posted February 9, 2022 Author Share Posted February 9, 2022 I've tried adding this to the docker-compose.yml (even though this doesn't seem right, running as root), but that doesn't change anything. environment: - UID=0 - GID=0 Link to comment Share on other sites More sharing options...
Luke 37167 Posted February 15, 2022 Share Posted February 15, 2022 Hi, please see if this similar question here helps: Thanks. Link to comment Share on other sites More sharing options...
Xinv9 0 Posted February 15, 2022 Author Share Posted February 15, 2022 Thank you. Unfortunately this doesn't help me. That other question is also not solved by the way. It did help me with the correct statement to exec into the container, but once there I can do everything write/delete, without a problem. Also in the mounted folders. But the Emby-error persists. Link to comment Share on other sites More sharing options...
focheur91300 0 Posted February 15, 2022 Share Posted February 15, 2022 Hello, I had the same problem on a Debian 11. The only solution was to upgrade to the Emby beta. Sincerely Link to comment Share on other sites More sharing options...
Luke 37167 Posted February 15, 2022 Share Posted February 15, 2022 7 minutes ago, focheur91300 said: Hello, I had the same problem on a Debian 11. The only solution was to upgrade to the Emby beta. Sincerely Hi, it's due to a bug in the .NET runtime, and the upcoming 4.7 server release has updated to .NET 6, which resolves this. Link to comment Share on other sites More sharing options...
Xinv9 0 Posted February 15, 2022 Author Share Posted February 15, 2022 Aargh, this indeed solved the problem, tnx @focheur91300. Well at least I learned a lot about Docker and permissions... Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now