Mirrored mode networking cannot handle port bindings like *:8080.

[hour-keeper]

Windows Version

Microsoft Windows [Version 10.0.26100.4351]

WSL Version

2.5.7.0

Are you using WSL 1 or WSL 2?

• [x] WSL 2
• [ ] WSL 1

Kernel Version

6.6.87.1-microsoft-standard-WSL2

Distro Version

Alpine v3.21

Other Software

Rancher Desktop (Windows): Version 1.19.1

Repro Steps

1.Edit the docker-compose.yml file and run the SuperNG6/docker-aria2 image with disable webui and the containerrrr/watchtower image with http api mode enabled and network_mode: host 2.docker compose up -d

Expected Behavior

localhost:8080 and localhost:6800 return the correct results.

Actual Behavior

At this point, you will find that port 8080 on the windows host network is not accessible. At this point, we found that port localhost:8080 (actually 127.0.0.1:8080) is inaccessible on the windows host network, and port localhost:6800 (actually 127.0.0.1:6800) is accessible. Use the rdctl shell to enter the rancher-desktop wsl VM and use the ss command to check that the two ports are not accessible. Using the rdctl shell to enter the rancher-desktop wsl virtual machine and using the ss command, we found that the two ports are bound to 0.0.0.0:6800 and *:8080, respectively.

Diagnostic Logs

No response

[github-actions[bot]]

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 script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

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'.

[hour-keeper]

/emailed-logs

[github-actions[bot]]

Diagnostic information

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