microsoft / microsoft/AzureTRE
New container builds have `/home/vscode/.config/` folder owned by root
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Describe the bug
Newly built devcontainers have the ownership of the .config folder for the vscode user set as follows:
drwxr-xr-x 2 root root 4096 Jun 22 14:50 .config
This leads to error messages about processes not being able to write to that folder, such as:
mkdir: cannot create directory ‘/home/vscode/.config/vscode-dev-containers’: Permission denied
Steps to reproduce
- Build a new devcontainer for Azure TRE
- Run the devcontainer
- Open a terminal in VSCode in the devcontainer
Azure TRE release version (e.g. v0.14.0 or main): v.0.17.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by building a new Azure TRE devcontainer, running it, and opening a VSCode terminal as described. Inspect the container setup responsible for creating /home/vscode/.config; done means the folder is owned by vscode and processes can create /home/vscode/.config/vscode-dev-containers without a permission error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100