-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review/add commands to be surfaced when connected from WSL #5765
Comments
Documentation updated and confirmed that the command was renamed |
Reopening so that @c0g1t8 can add more details about the specific scenario on WSL2. |
This is a follow up to my comment - microsoft/vscode-docs#4908 (comment). Remote-Containers extension does not behave in WSL2 as expected. Remote-Containers: Try a Development Container Sample... is not available when remoting to WSL2. I've been able to confirm this with WSL2(Ubuntu 20.04) on both Windows 10 Pro and Windows Pro 11. The expectation is that the extension should behave the same in WSL2 as in Windows. I believe the issue lies with the VS Code server running in Linux. That's a guess.🤔 |
Related: #5014 We show only part of the commands when connected with Remote-WSL. This was to avoid overloading the UI with commands. As Remote-WSL (and to a degree Remote-SSH) more and more becomes a starting point for Remote-Containers connections, we can make some of these commands also available while already connected with Remote-WSL. |
Updated with changes for #2994. |
Remote-Containers: Try a Sample is not available as a command.
I've already filed an issue in the Visual Studio Code documentation repository - microsoft/vscode-docs#4908
The text was updated successfully, but these errors were encountered: