1471

There are a few good use cases for root shares, Space Invader One has a recent video on it: Unraid & Moving Data (Part 4) RootShares And also covered in this older video with lots of other useful tips and tricks with SMB shares: Unraid Shares in Depth - PT1 Windows and SMB __________________________________________________________________________________ Thanks for the reply. Yes that was my first though, however permissions for most other folders and files in the share are being changed too, so harder to track down as have lots of container mapped to the whole array. I can at least narrow it down to container that have access to the share though. There were a few containers without a PUID and PGID variable, so added those, but that didn't fix the problem. Think the next step is to look at umasks, I've ssh'd into each container and they've all running under 0022. Had some good advice in the unraid subreddit, sounds like changing umasks to 002 or 000 where supported might work? Not sure if the permission changes are something that would show up in the logs? If so, any idea what I should be looking for?

I've got a odd problem with file and folder permissions changing every few days. I Imagine this this is a container with the wrong permissions or something, however I've only been using Unraid for a few weeks and would appreciate pointing me in the right direction to find whats wrong. I have a fair few containers and a Server2019 VM, with shares mapped via a root share. This works well but every few days the permissions change and no longer have edit rights to the shared folder. This is the same when mapped to the share in my VM or connecting from ym Macbook. Running the tool 'docker safe perms' fixes the permissions but they keep reverting. I've run ls -al before and after fixing the permissions so can see whats being changed, see attached screen shot. I've also attached my servers diagnostics for info. If it's relevant, these are my root share settings: [root share] path = /mnt/user comment = browseable = no valid users = olly-share write list = olly-share vfs objects = #hide files veto files = /._ds*/.DS_Store/ hide files = /$*/ hide dot files = yes #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end Any idea how I can find whats changing the permissions? I've had a look through the logs, but not really sure what i'm looking for. I've been through my containers and found a few that didn't have a PUID or PGID set, so i've added those variables to see if that makes a difference, but not entirely confident in what i'm doing when it comes to docker permissions to be honest. unraid-server-diagnostics-20210604-1123.zip

Thanks for the info. Yup, setting the variable to 'secure' does then prompt for a password if trying to perform an action which is good. I just need to try and figure out how to authenticate to access the api in Grafana now.

Thanks for the awesome container, really useful for Unraid metrics in Grafana. I'm having problems securing the container using the method suggested though, any ideas what i'm doing wrong? I've changing the container variable 'KeyStorage' from config to secure but can still access the api without a username/password prompt, with the following in the logs: Error: ENOENT: no such file or directory, open 'secure/mqttKeys'