You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 with
When 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
Create a docker compose
Include the environment variable of UMASK=000
start container
open a shell into the container and run umask and see umask is still set to 022
create some files by grabbing a torrent and notice the permissions it creates.
open a shell into the container and run umask and see umask is still set to 022
This is not a valid test, as variables are not passed to this shell by default. you can run /usr/bin/with-contenv bash to get a shell aware of container variables (qbit is started with this awareness)
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.
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: