vscode-remote-release
https://github.com/microsoft/vscode-remote-release
Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
not yet supported2 Subscribers
Add a CodeTriage badge to vscode-remote-release
Help out
- Issues
- Declarative secret support in Dev Containers
- Dev Containers - "Attach to Running Container..." Error: ENAMETOOLONG: name too long
- Add Folder to Workspace inside container displays error
- DevContainer + Remote SSH: Host server: X11 connection rejected because of wrong authentication
- code command not available in postcreatecommand when using devcontainers
- Can't attach VSCode Docker when using VSCode Tunnels connect.
- Compose: Use default `workspaceFolder` and mount point
- Can't attach to devcontainer "ln: failed to access ‘/tmp/user/1000/vscode-wayland-xxxxxx.sock’: Permission denied"
- Udocker
- Claims that black is invalid as a formatter
- Docs
- not yet supported