![]() You could also use the UMASK variable to do what I suggest in the other thread the first bit (normally untouched) is the SET mode for the file - this can be 0 (normal file or directory), sticky, GID, UID, etc. Thanks for the info and the time to dig it up. not exactly light reading so looks like project for tonight. Should I just remove the values? or should they be changed? I looked back and the older Plex Docker did not have any settings for these values. They have numerical values: PUID = 99 and PGID = 100. (P=Plex is an assumption on my part but I think GID and UID is correct). I think this stands for Plex UserID and Plex GroupID. There are values in the docker settings for PGID and PUID. (Hopefully, someone who uses this Docker will see this thread and jump in to help out.)ĮDIT By the way, google is your friend if you want detailed information on permissions, 'owner', 'group' and 'other'. ![]() Someone should know where that setting in this Docker. And those settings are wrong for Unraid! This problem is not that usual. What the problem is that the Plex Docker that you are using has settings somewhere that instructs it how to assign permissions the directories and files that it creates. While 'nobody' is the owner, in Unraid that means that there is no owner, The group- users in this case - 'permissions' would be that logged-in user is assigned to the 'group' for that share (The Private and Secure Share security settings will have users assign to allow controlled access to the share), the 'other' permissions are for the anonymous user. OK, it means that no one (except for root) has permission to do anything but read the files inside. Obviously I see the "write" permissions missing but not sure what the full sequence means or how to adjust.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |