Hello,

I am working with a docker container, which does not support PUID, PGID, or UMASK environment variables. The container is available here: https://github.com/juaniwck/mister-retroarch-save-sync

I am currently having an issue where the container is creating new files with the following permissions: -rw-r--r--

I have attempted to add the necessary environment variables via the Docker configuration UI, as well as adding "--user 99:100 --env UMASK=000" as additional parameters. In both cases, new files continue to be written with the following permissions: -rw-r--r--

Ultimately, I want the docker to write directories with the following permission: drwxrwxrwx and for files: -rw-rw-rw-.

Are there any suggestions for how I might force the correct permissions to be applied?

DISCLOSURE: I am not a Docker Container expert!

It was not clear to me from your post of how you were trying to setup the PUID, PGID and UMASK variables. Here is a post which explains how I did it for one container:

https://forums.unraid.net/topic/188600-share-permissions-changed-to-owner-99/#findComment-1540351

1 hour ago, Frank1940 said:

DISCLOSURE: I am not a Docker Container expert!

It was not clear to me from your post of how you were trying to setup the PUID, PGID and UMASK variables. Here is a post which explains how I did it for one container:

https://forums.unraid.net/topic/188600-share-permissions-changed-to-owner-99/#findComment-1540351

Thanks so much for the assistance and apologies for the lack of clarity in my original post. The method you outlined in your linked post was how I attempted to set the PUID, PGID and UMASK variables.

I also tried to add: "--user 99:100 --env UMASK=000" as extra parameters, shown below:

Some applications have a way to set umask in their user interface, NZBGet for example. Others may have a setting in one of their appdata files, transmission has a umask in setting.json.

1 hour ago, JPilla415 said:

I also tried to add: "--user 99:100 --env UMASK=000" as extra parameters, shown below:

the --user should create all new files with the correct ownership, but wont change the perm.

and when looking into the git page there seems to be no variable therefore, and as your issue request from 2 weeks is still open

alternative solution, depending now how fast you need the changes

user script which will either

act as watchdog (inotify) and change perms pretty instant

scheduled like "hourly" and just change file and folder permissions

just as alternative suggestion until the docker maintainer may add this function to his docker.

8 hours ago, JPilla415 said:

Thanks so much for the assistance and apologies for the lack of clarity in my original post. The method you outlined in your linked post was how I attempted to set the PUID, PGID and UMASK variables.

I also tried to add: "--user 99:100 --env UMASK=000" as extra parameters, shown below:

Not quite the method I used. here is a walk through:

1– Left-click on the icon of the container.

Then click on 'Edit':

2– Go to the bottom of the page. click on the 'Show more setting...' dropdown menu.

Check and see if PUID, PGUI and UMASK variable are already defined. If they are– edit them.

3– If one or more are missing, add them by clicking here:

4– Then follow the instructions from here:

https://forums.unraid.net/topic/188600-share-permissions-changed-to-owner-99/#findComment-1540351

5– When done, it will look something like this:

The first items were already there. The Variables– PUID, PGID and UMASK –were the ones which I had to add for this container.

Hope this helps....

Edited Friday at 11:33 AM2 days by Frank1940

12 hours ago, trurl said:

Some applications have a way to set umask in their user interface, NZBGet for example. Others may have a setting in one of their appdata files, transmission has a umask in setting.json.

Thanks, this Docker container has no appdata files to edit.

4 hours ago, Frank1940 said:

Not quite the method I used. here is a walk through:

1– Left-click on the icon of the container.

Then click on 'Edit':

2– Go to the bottom of the page. click on the 'Show more setting...' dropdown menu.

Check and see if PUID, PGUI and UMASK variable are already defined. If they are– edit them.

3– If one or more are missing, add them by clicking here:

4– Then follow the instructions from here:

https://forums.unraid.net/topic/188600-share-permissions-changed-to-owner-99/#findComment-1540351

5– When done, it will look something like this:

The first items were already there. The Variables– PUID, PGID and UMASK –were the ones which I had to add for this container.

Hope this helps....

My last post may not have been clear, but the process you outlined is the first step that I tried. I also tried the extra parameters route. Thanks very much for the suggestion though.

10 hours ago, alturismo said:

the --user should create all new files with the correct ownership, but wont change the perm.

and when looking into the git page there seems to be no variable therefore, and as your issue request from 2 weeks is still open

alternative solution, depending now how fast you need the changes

user script which will either

act as watchdog (inotify) and change perms pretty instant

scheduled like "hourly" and just change file and folder permissions

just as alternative suggestion until the docker maintainer may add this function to his docker.

Yea, I think that the docker was created using AI tooling, and the developer seems to have moved on to other projects. I worry that it will be abandoned, which is why I am looking into other solutions.

I will look into producing a script. Thanks.