microsoft / microsoft/vscode-remote-release
Open in container from WSL
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
When using both the devcontainers and WSL extensions, it is currently not possible to directly jump into a devcontainer from a WSL remote VSCode. Currently, I have to "reopen in Windows" and then jump into the container from Windows.
Is it possible to add the functionality for jumping into a devcontainer directly from a WSL session?
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 reproducing the reported workflow with the devcontainers and WSL extensions: begin in a WSL remote VS Code session and attempt to open a devcontainer. Review the existing remote-development entry points involved in reopening in Windows and opening the container. Done means a WSL remote session can jump directly into a devcontainer without reopening in Windows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, vscode
- Domain
- devtools, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100