You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Linux version 5.15.167.4-microsoft-standard-WSL2 (root@f9c826d3017f)
Distro Version
Ubuntu 22.04
Other Software
VS Code 1.96.4
Extensions:
WSL 0.88.5
Docker 1.29.4
Devcontainers 0.394.0
Docker 27.2.0, build 3ab4256 (installed into WSL by devcontainers extension last year)
Also been playing with the devontainer feature docker-in-docker, which may or may not have polluted my wsl network config.
Repro Steps
In ~/.wslconfig: (commented settings were also tried with no effect)
Able to talk to the internet and intranet (which works with regular NAT networking mode)
Actual Behavior
# names have been anonymized
devcontainers@my-laptop:/mnt/d$ curl google.com
curl: (6) Could not resolve host: google.com
devcontainers@my-laptop:/mnt/d$ curl gitlab.corp.internal
curl: (6) Could not resolve host: gitlab.corp.internal
devcontainers@my-laptop:/mnt/d$ ping 8.8.8.8
ping: connect: Network is unreachable
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!
Maybe it's also worth mentioning that my Windows and Hyper-V networking stack might have leftover garbage in it from tons of unrelated HCI VM experiments, that could be interfering with whatever autodetect magic is done by wsl. Let me know if and how I can provide more details if interested.
Windows Version
Microsoft Windows [Version 10.0.26100.3037]
WSL Version
2.3.26.0
Are you using WSL 1 or WSL 2?
Kernel Version
Linux version 5.15.167.4-microsoft-standard-WSL2 (root@f9c826d3017f)
Distro Version
Ubuntu 22.04
Other Software
VS Code 1.96.4
Extensions:
Docker 27.2.0, build 3ab4256 (installed into WSL by devcontainers extension last year)
Also been playing with the devontainer feature docker-in-docker, which may or may not have polluted my wsl network config.
Repro Steps
In
~/.wslconfig
: (commented settings were also tried with no effect)wsl --shutdown
thenwsl
then:Expected Behavior
Able to talk to the internet and intranet (which works with regular NAT networking mode)
Actual Behavior
# names have been anonymized devcontainers@my-laptop:/mnt/d$ curl google.com curl: (6) Could not resolve host: google.com devcontainers@my-laptop:/mnt/d$ curl gitlab.corp.internal curl: (6) Could not resolve host: gitlab.corp.internal devcontainers@my-laptop:/mnt/d$ ping 8.8.8.8 ping: connect: Network is unreachable
Diagnostic Logs
WslNetworkingLogs-2025-02-05_10-16-24.zip
The text was updated successfully, but these errors were encountered: