microsoft / microsoft/vscode-remote-release
Devcontainers CLI does not finish running in WSL
Open
@chrmarti is already working on this.
Since Dec 9, 2024.
bug
containers
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
- VSCode Version: 1.96.0-insiders
- Local OS Version: Windows 11
- Remote OS Version: Unknown
- Remote Extension/Connection Type: Dev Containers
Steps to Reproduce
- Install devcontainers CLI on Windows
- Run
devcontainer-insiders --help - 🐛 The following help text is printed, but the command does not terminate. The user must manually input Ctrl+C to issue the next command.
devcontainer-insiders --help
Checking for Dev Containers CLI
Checking for Dev Containers CLI
I tried deleting ~/.vscode-remote-containers and reinstalling the devcontainers CLI, but got the following non-terminating command:
devcontainer-insiders --help
Checking for Dev Containers CLI
Checking for Dev Containers CLI
Copying Dev Containers CLI
Run in Host: tar --no-same-owner -x -f -
.
./gitAskPass.sh
./bootstrap.Dockerfile
./inspect-volume
./ssh-askpass.bat
./ssh-askpass.sh
./updateUID.Dockerfile
./inspect-volume/.devcontainer.json
./inspect-volume/volume.Dockerfile
Run in Host: tar --no-same-owner -x -f -
PATH
I have confirmed my path only references the devcontainer CLI once with the entry c:\Users\raymondzhao\AppData\Roaming\Code - Insiders\User\globalStorage\ms-vscode-remote.remote-containers\cli-bin.
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.