-
Notifications
You must be signed in to change notification settings - Fork 822
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
WSL2 with hostAddressLoopback - docker-ce bridge network unreachable from Windows #11758
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The scipt will output the path of the log file once done. Once completed please upload the output files to this Github issue. Click here for more info on logging View similar issuesPlease 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! Open similar issues:
Closed similar issues:
|
Windows Version
Microsoft Windows [Version 10.0.22631.3737]
WSL Version
2.0.14.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-1
Distro Version
Ubuntu 24.04
Other Software
Docker CE 27.0.3
Repro Steps
.wslconfig
...Expected Behavior
Re-raising moby/moby#48136 here as requested - @CatalinFetoiu.
Reported by @dannyhpy in moby/moby#48075 (comment) ...
Actual Behavior
Packets arrive on the WSL2 guest's
ethN
interface, with the shared host address as the source. So, everything looks normal. They're DNAT'd, arrive at the container, and get a response addressed to the shared host address (192.168.1.100
in the example). But, the response packets don't get back to the WSL2ethN
interface.That's because the dest MAC address in response packets belongs to the docker network's bridge (the container's default gateway). The WSL2 guest has that IP address itself, on its own
ethN
, it doesn't know anything about the Windows version of that address. So, packets are delivered locally rather than sent back toethN
- then dropped because nothing in the Linux guest is listening on that dest port.Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: