microsoft / microsoft/vscode-remote-release
second wsl2 user causes /tmp/remote-wsl-loc.txt permission denied
Open
Nobody has claimed this yet.
bug
plan-review
wsl
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
reproduction steps:
- create typical wsl2 install with ubuntu
- open windows terminal into that
- run
code . - create a second wsl user (e.g.
foo) - open terminal into that user (
wsl --user foo) andcdto foo home - run
code .
shows cannot create /tmp/remote-wsl-loc.txt: Permission denied
ls -l /tmp/remote-wsl-loc.txt will show first user/group ownership of that file
Environment
code --version
1.58.2
c3f126316369cd610563c75b1b1725e0679adfb3
x64
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
Reproduce the two-user WSL2 setup using wsl --user foo and code ., then inspect /tmp/remote-wsl-loc.txt and its ownership after the first user's launch. Done means the second user's code . no longer fails with a permission-denied error for that file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, ubuntu, vscode
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100