microsoft / microsoft/vscode-remote-release
VS Code Devcontainer CLI wrapper does not support user input in up and exec commands
Open
@chrmarti is already working on this.
Since Sep 13, 2024.
bug
containers
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
- VSCode Version: Version: 1.94.0-insider (Universal)
- Local OS Version: macOS 14.6.1 (23G93)
- Remote OS Version: probably irrelevant (but I've tested with an Alpine 3.20 image)
- Remote Extension/Connection Type: Containers
Steps to Reproduce:
- Set up a directory with a devcontainer configuration at
$DIR. I used an empty directory aside from the following.devcontainer/devcontainer.jsonfile:{ "name": "Alpine", "image": "mcr.microsoft.com/devcontainers/base:alpine-3.20" } - Run
devcontainer up --workspace-folder "$DIR"to set up the devcontainer - Run
devcontainer exec --workspace-folder "$DIR" /bin/shto open a shell - Enter any command in the shell.
With the devcontainer CLI installed through VS Code (Dev Containers: install devcontainer CLI), the up and exec commands do not react to any form of interactive input. In particular, the shell opened in step 3 is unusable because it doesn't react to any commands typed in, and instead just hangs. If the up step expects interactive input at any point, it will also just hang.
With the devcontainer CLI installed through npm install -g @devcontainers/cli, input is handled as expected.
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.