unRAID OS Version:

v6 b15

 

Description:

using the docker ui in unraid, if you add a docker container and specify a new folder to create for the host path volume mapping then it incorrectly creates it with permissions set as user root, group root, which then prevents the docker container from starting (if docker container is running as user nobody).

 

How to reproduce:

start unraid webui

goto docker tab

click on "add container"

specify a host path volume mapping to an existing path on the cache drive and append the name of the container to the pathname (this will then force creation of a new folder)

click create

 

try and create a file/folder on the host path volume mapping, you will receive permission denied, due to the fact that the new folder has been created as user root, group root and NOT the correct user nobody group users

 

Expected results:

ability to create files/folders as user nobody (i.e. what the container will be normally running as)

 

Actual results:

docker container cannot run due to incorrect permissions set, permission denied when using a client pc to navigate to the newly created config folder

 

Other information:

the file system im using on the cache drive is BTRFS, probably not relevant but hey just in case it is :-)

 

if you need any more info then please let me know.

Tried this with -rc2, seems to work.  Can you verify please?

Thanks Tom, currently holding out for rc3, will post here once it's released and tested.

confirmed fixed in RC3, i shall change the OP