Skip to content
This repository has been archived by the owner on Jul 16, 2023. It is now read-only.

UMASK setting seems to be ignored. #181

Open
gderf opened this issue May 6, 2023 · 0 comments
Open

UMASK setting seems to be ignored. #181

gderf opened this issue May 6, 2023 · 0 comments

Comments

@gderf
Copy link

gderf commented May 6, 2023

The system UMASK is set to 022 and when I create directories and files in the shell as my ordinary unprivileged user their permissions are properly set as 755 and 644 as expected.

In my docker yaml file I have:

environment:
  - PUID=1001
  - PGID=100
  - UMASK=022

In the container log file I see:

05/06/2023 3:21:43 PM 2023-05-06 19:21:43.232074 [INFO] UMASK defined as '022'

However directories and files being created by the container are set to 775 and 664. This corresponds to a UMASK of 002, which is the default for the image if left unset.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant