Write Permissions for Windows on SMB share?

[spike32]

First of all, I am not having issues getting my shares to read on my Windows machines, but I want my Windows machines to have permission to write to folders. I have all my docker containers set to nobody:users like suggested, but I have to set my media folders that way too else they won't work proper with the containers.

 

I want to be able to add, delete, etc from my Windows machines. I have a user that is set up with read/write in the users tab, but it doesn't work for this issue. The only thing I can do is chmod 757 or 777 the folders so I have permission, but that obviously isn't the right way to go.

[Frank1940]

First thing.  I am going to point you to a thread about setting Unraid/Windows so that they work together.

 

     https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-1011-smb-setup/

 

Understand that the folders/files that you write will the Share Access user will be the name that shows up as the owner of the resource.  The group will always be users.  All the Share Access logins are members of the   users   group!  So Share Access users can have full access to the share ( assuming you set up the permissions on the share to allow this)  by virtue of being a member of the group! 

 

Second thing.  Regarding the Dockers that write to the share.  Not all of the Dockers that are available via the APPS tab are configured to work properly with Unraid!  From this post, I am providing the quoted information:

 

        https://forums.unraid.net/topic/131730-update-from-69-to-6115-and-got-permission-denied/#comment-1219731

Quote

I set the following settings in each of my dockers to fix ownership and permission problems:

PUID = 99

PGID = 100

UMASK = 000

PUID of 99 equates to "nobody", PGID of 100 equates to "users", and UMASK of 000 allows for full access.

 

You will have to edit your Docker containers if they are not writing files to the array with the proper owner, group and permissions.  All of the Docker continers that I have seen have these fields available for editing.  You may have to do a little looking as they may be hidden until you click on some switch in the Edit menu to display them...

Edited June 30 by Frank1940

[Frank1940]

11 hours ago, spike32 said:

The only thing I can do is chmod 757 or 777 the folders so I have permission, but that obviously isn't the right way to go.

There is a utility to fix the permissions.   TOOLS    >>>    New Permissions    Be sure to read the instructions.  There are two dropdown lists so be sure you look at both before you start.  You should probably use the Shares option and do not select appdata  as it will generally screw up all of the Docker containers if you do! 

[spike32]

On 6/30/2024 at 9:37 PM, Frank1940 said:

There is a utility to fix the permissions.   TOOLS    >>>    New Permissions    Be sure to read the instructions.  There are two dropdown lists so be sure you look at both before you start.  You should probably use the Shares option and do not select appdata  as it will generally screw up all of the Docker containers if you do! 

 

Thanks, and thanks for the tip on appdata! Very helpful. Do you know how to make it so any future folders made or files made will have those permissions by default? I keep finding files and stuff I don't have access to and I have to keep re-running it or doing it manually.

[Frank1940]

3 hours ago, spike32 said:

Thanks, and thanks for the tip on appdata! Very helpful. Do you know how to make it so any future folders made or files made will have those permissions by default? I keep finding files and stuff I don't have access to and I have to keep re-running it or doing it manually.

 

Most of the time, this occurs when a Docker (or VM) is writing directly to the Array or a pool.  So what you have to do is figure out which one it is.  Or go to each docker (and VM) that can save data and do what was suggested in this post in this thread:

 

On 6/30/2024 at 5:01 PM, Frank1940 said:

Second thing.  Regarding the Dockers that write to the share.  Not all of the Dockers that are available via the APPS tab are configured to work properly with Unraid!  From this post, I am providing the quoted information:

 

        https://forums.unraid.net/topic/131730-update-from-69-to-6115-and-got-permission-denied/#comment-1219731

Quote

I set the following settings in each of my dockers to fix ownership and permission problems:

PUID = 99

PGID = 100

UMASK = 000

PUID of 99 equates to "nobody", PGID of 100 equates to "users", and UMASK of 000 allows for full access.

Expand  

 

You will have to edit your Docker containers if they are not writing files to the array with the proper owner, group and permissions.  All of the Docker continers that I have seen have these fields available for editing.  You may have to do a little looking as they may be hidden until you click on some switch in the Edit menu to display them...