microsoft / microsoft/vscode-remote-release
The 'devcontainer' cli included with remote-containers hangs when used in WSL2 prompts
Open
@chrmarti is already working on this.
Since May 15, 2024.
bug
containers
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
- VSCode Version: 1.89.1 (system setup)
Commit: dc96b837cf6bb4af9cd736aa3af08cf8279f7685
Date: 2024-05-07T05:13:33.891Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0 - Local OS Version: Windows_NT x64 10.0.22621
- Remote OS Version: Debian GNU/Linux 12 (bookworm)
- Remote Extension/Connection Type: WSL2
Steps to Reproduce:
- Find out the path to the devcontainer cli
- e.g.
c:\Users\yourname\AppData\Roaming\Code\User\globalStorage\ms-vscode-remote.remote-containers\cli-bin\devcontainer
- e.g.
- Convert to a WSL path
- e.g.
/mnt/c/Users/yourname/AppData/Roaming/Code/User/globalStorage/ms-vscode-remote.remote-containers/cli-bin/devcontainer
- e.g.
- Run it inside a WSL prompt with any command or options like
--version
/mnt/c/Users/yourname/AppData/Roaming/Code/User/globalStorage/ms-vscode-remote.remote-containers/cli-bin/devcontainer --version
The command never completes and you must press CTRL+C or CTRL+Z to terminate it.
The devcontainer open command doesn't work at all in WSL2.
Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes
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.
Assessment
This issue has not been assessed yet.