Docker created folder now has read only permissions for smb user

Hey,

this is probably a very simple issue but I don't get how it came to be.

I setup a containter that contained the following volume:

- /MEDIA/downloads:/downloads

That worked fine, volume got created and the container has no issue writing in the folder.

The issue that my SMB account now has only read access to the downloads and sub directory.

This is the output for

ls -lr /MEDIA/

$ ls -al /MEDIA/
total 60
drwxrwsr-x  1 root    users   118 May 13 11:50 .
drwxr-xr-x  1 root    root     18 May  6 10:14 ..
drwxr-sr-x  1 appuser users   104 May 13 11:48 downloads
drwxrwsr-x  1 root    users    36 May  9 22:07 entertainment
$

As you can see, the owner of downloads as wanted is appuser, but write access for users seems missing. I can figure out how to re-add that permission even without reset permissions, but I don't get why it was setup that way to beginn with.

What did I screw up?

Greetings.

Quote from chente

Not knowing which container did this, I assume that container created that folder, and by default it will do so with read-only permissions.

If you want to make sure that doesn't happen you can create the folder before launching the container.

To fix it simply change the permissions of that folder. The container will continue to function without issue.

Was a bitorrent container. Assumed that wasn't relevant.

If I create the folders beforehand it will be owned by my ssh account - could that pose a problem for any containers? I've tried avoiding this since I'm uncertain on the effects of that.

Quote from chente

Creating the folder ahead of time shouldn't be a problem, as long as you create that folder with access permissions for the user defined in the container.

One way to ensure that is to create the folder with read and write permissions for the users group and that user is in the users group. There are other ways to do it.

Okay. That I can do easily.

But I just noticed that my beginning issue is not fixxed.

As is the nature of a downloads folder, the container will create frequently subfolders in there.

And as I just noticed - those, just as well as the top folder are read only for my SMB user.

I can (and have) changed the permissions of the /MEDIA/downloads parent folder, but it seems a big hassle to manually do this for every sub folder that will be created there.

So how can I shut that behaviour down?