So, I haven't made any changes tonight but I made this observation through the terminal on my Synology: PS Do you know the version of Docker running on your synology device and is there any userns mapping going on? Edited Maby hurricanehrndz
If you are able to figure out what is going on, please let me know and I will try and fix any issues with the container itself. Has anyone seen this behavior? Am I missing anything? I've also tried setting the APP_UID and APP_GUID to one of my Synology users and that didn't work either. It's also worth noting that when I use the terminal as root in the container I can view my media folders just fine so it's only the default "appuser" that cannot access my media folders. I've reviewed the permissions for both the "docker" folder and my media folders and I don't see any glaring differences that would prevent reading my media folders. However, as I mentioned above Emby cannot write to any other folder I mount to the container. I've mounted that to my Emby container and Emby has no problem writing the necessary configuration files there. What I find most interesting is that when I installed Docker it created a shared folder named "docker".
When I hit Emby and try and set up my media folders I get a permission denied error in the Emby logs. I've launched the container and mounted the shared folders on the NAS to specified mount points using the Synology Docker launch wizard. I have a Synology DS716+ (latest software) with the Docker package installed.
0 kommentar(er)
