UNRAID mess with file permissions

[L0rdRaiden]

I have a user (storage) with read and write access to all my shares

 

this is my samba configuration

 

So in reallity I have read permisions to all shares but for writting persmisions I can only edit in some folders of some shares. The only clue I have is that those folders are old, they have existed almost since I started with unraid many years ago, by in recently created folders I don't have write permissions.

 

For example here I can not edit the folders in green, this folders are created by unraid.

 

 

I am using the storage user via SMB, I can edit adguardhome.yaml, but I can not edit adguardhome.yaml.bak

 

Do you know what could be the issue?  why unraid started to write files and folders with different permisions?

How can I restore all the file permissions to the "standard"? what are the best practices in unraid?

Also before I was using Code Server docker to edit configuration files for other dockers, at some point I lost that permisions as well and code server docker can only read files but not edit.

 

 

 

 

 

 

Edited October 26, 2022 by L0rdRaiden

[itimpi]

It is normal for any folder/file to not have permissions over the network if it is owned by ‘root’ as that user only has access to shares if they are set to be ‘public’.

 

looking at the folders you mentioned then it looks as if they are folders within the ‘appdata’ share used by docker containers?   If so then the permissions are set by the docker container and not by Unraid.