WSL 2.2: networkingMode=mirrored makes Podman unable to forward ports for Kind cluster

[bricss]

Windows Version

Microsoft Windows [Version 10.0.22631.3447]

WSL Version

2.2.2.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.150.1-2

Distro Version

Fedora Linux 39 (Container Image)

Other Software

Podman: v5.0.1
Podman-desktop: v1.9.1

Repro Steps

1. Create Podman Machine with the following .wslconfig:

[experimental]
autoMemoryReclaim=dropcache
hostAddressLoopback=true
sparseVhd=true
useWindowsDnsCache=true
[wsl2]
dnsTunneling=true
networkingMode=mirrored

2. Create Kind cluster with Podman-desktop app
3. Try to reach cluster from within Windows host machine

Expected Behavior

Created Kind cluster should be reachable at: https://localhost:<port>/

Actual Behavior

Two types of errors atm, with networkingMode=mirrored being enabled:

• connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
• connectex: No connection could be made because the target machine actively refused it.

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

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
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

[bricss]

/emailed-logs

[github-actions]

Diagnostic information

Found '/emailed-logs', adding tag 'emailed-logs'

[chanpreetdhanjal]

Hi. Can you please collect networking logs by following the instructions below?
https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues

[bricss]

Done, emailed logs 📧

[chanpreetdhanjal]

Thanks

[keith-horton]

Hi @bricss . Does your container solution leverage port forwarding from the root to the container? If so, we've identified compat issues and are working on a fix.

[bricss]

That's a great news 🙂
And I assume the answer for the question is yes, bcos I'm using podman machine in rootful mode 🤖

[benhillis]

Fixed with https://github.com/microsoft/WSL/releases/tag/2.3.11.