Open lynndixon opened 4 days ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
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)
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