microsoft / microsoft/vscode-remote-release
stuck with `opening remote` because of the `WSL` extension cannot work with `networkingMode=mirrored` in `~/.wslconfig`
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Is there an existing issue for this bug?
- I have searched the existing open issues and found none that apply.
- If I find any issue of interest that is related or closed, I will included a link to it in this issue.
Required Troubleshooting Steps
- I have read and performed the troubleshooting steps
- I have tried both values of the
remote.SSH.useLocalServersetting - My issue was not covered in the Tips and Tricks linked from the Troubleshooting Wiki.
- I will include a complete copy of my Remote - SSH logs by running Remote-SSH: Show Log in the command palette or from View > Output in the menu bar
[Optional] Diagnose with Copilot
I did not ask the @remote-ssh participant for help
In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?
I did not try step 2 of the troubleshooting steps
Remote-SSH Log
Same issue with this one: https://github.com/microsoft/vscode-remote-release/issues/7486, and the reason and solution is https://github.com/microsoft/vscode-remote-release/issues/7486#issuecomment-2183139998.
Seems like the VSCode WSL extension cannot work with the config networkingMode=mirrored in ~/.wslconfig.
My Env:
- Host: win 11 23h2
- wsl: Ubuntu-24.04, Linux 5.15.167.4-microsoft-standard-WSL2 #1 SMP Tue Nov 5 00:21:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
~/.wslconfigin host:[wsl2] processors=12 memory=16GB swap=8GB networkingMode=mirrored autoProxy=true dnsTunneling=true/etc/wsl.confin wsl:[boot] systemd=true [automount] options="metadata,dmask=0022,fmask=0133"- VSCode v1.91.1, installed in host
- WSL extension v0.88.5
Expected Behavior
With setting networkingMode=mirrored in ~/.wslconfig in host, VSCode still can be run in wsl code . to open a folder in wsl, opening remote successfully.
Actual Behavior
after running code ., vscode stuck with opening remote
Steps To Reproduce
Anything else?
No response
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.