umask doesn't seem to be respected for the devcontainer process/instance #9041
Labels
containers
Issue in vscode-remote containers
feature-request
Request for new features or functionality
Milestone
Is there an existing issue for this bug?
Required Troubleshooting Steps
remote.SSH.useLocalServer
settingConnect Locally
It connects successfully
->
Im running an amazon al2023 image in a remote devcontainer. I have the following in the Dockerfile with hopes that files created within the container on mounted shares are read writeable by the dev team members.
$DATA_HOME above will be a mounted volume.
Within the VSCode's devcontainer, if i open a terminal and touch a file on the share, the permissions are fine - they are read writeable by the group. However, if i use visual studio code to create a file (File->New File), the file is r/w by only me. I was looking through the devcontainer build/start logs and noticed the following:
Not sure if that is the mask that is used for the devcontainer process/instance...but if it is, how would i change that to 0002?
Or is there another solution for solving this issue?
It is quite a productivity problem when we constantly have to reach out to team members of admins to change file permissions
Thanks much
Expected Behavior
To be able to set umask at the devcontainer process level such that creation of files are group read/writeable on volumes shared by other members.
Steps To Reproduce
No response
Remote-SSH Log
Remote-SSH Log
Anything else?
Opening here as per request frrom devcontainer github here: https://github.com/orgs/devcontainers/discussions/73
The text was updated successfully, but these errors were encountered: