-
-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] UMASK variable is being ignored again #353
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
This is not a valid test, as variables are not passed to this shell by default. you can run |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is locked due to inactivity |
Is there an existing issue for this?
Current Behavior
It seems we may have a regression? I am attempting to adjust the UMASK for the running container. I have tried several iterations in my docker compose file, and am currently attempting to do
- UMASK=000
to test withWhen the container launches, I go into the shell and the output of running the umask command is still 022
Expected Behavior
I'd expect that setting the UMASk=003 or UMASK=000 be applied once the container is running.
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: