Default docker permissions should be....?

[Marshalleq]

Dear all, I hope you can help me first with a simple question, then assuming the answer is as I expect, an idea of where to begin to resolve.

 

 

Are the default docker permissions (i.e. appdata folder) meant to be root.root or nobody.users?

 

Mine seem to now be defaulting to root.root and this means the docker doesn't start, in fact it doesn't even create the docker config properly.  So I chown them into submission, but still when the docker starts and it needs to create other things in there - same problem and this is a challenge.

 

However, one app is complaining about a folder that IS set to nobody.users so I'm left wondering if my assumption is wrong.

 

I've also wondered if it's the docker template i.e. can a template be set with wrong permissions by the creator?  I'm about to check another one to see if they're all being created this way or just one.

 

Thankyou for any help.

 

Marshalleq

 

Edited October 11, 2019 by Marshalleq

[jpowell8672]

unRAID defaults to nobody:users for user:group permissions on the docker.

[jpowell8672]

I would just remove all dockers and also remove images then delete docker image. Let new docker image be created then just goto apps>previous apps and reinstall all apps.

[Marshalleq]

Thanks all, yes I've deleted a few times.  It comes back root.root.  I've just tested a few times with a) a previously uninstalled app that has UID and GID set in the docker template.  That came out as nobody.users.  I then tested with another one I've never installed that does not have UID and GID set in the template, that also came with nobody.users installed.  Then I tested with this latest app (Tdarr) from scratch (deleted folder) and that installed root.root.  I'll try delete image too now just to be sure, but I think I tried this before.  If someone wants to be super helpful and install Tdarr and tell me what permissions it comes up with that should confirm it's either an app template issue or it's an issue specific to me.

 

Many thanks for the quick responses all.

 

Marshalleq

[Marshalleq]

No need - deleting the container AND the image seems to have resolved.  Many thanks all.  Will see how it goes!

[jpowell8672]

You could also try the built in unRAID Tools>Docker Safe New Perms or after remove all dockers and before reinstalling try Tools>New Permissions.

[Marshalleq]

So I spoke to soon.  The root docker of the folder is correct, but inside that it has assigned permissions to one of the unraid users.  I have also been seeing this behaviour lately and I don't know why.

[Marshalleq]

I think it's the way the container is built.