Can not access container ports through VirtuioProxy
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
### Windows Version
Microsoft Windows [版本 10.0.26100.32690]
### WSL Version
WSL 版本: 2.7.3.0 内核版本: 6.6.114.1-1 WSLg 版本: 1.0.73 MSRDC 版本: 1.2.6676 Direct3D 版本: 1.611.1-81528511 DXCore 版本: 10.0.26100.1-240331-1435.ge-release Windows: 10.0.26100.32690
### Are you using WSL 1 or WSL 2?
- [x] WSL 2
- [ ] WSL 1
### Kernel Version
默认分发: Ubuntu-24.04 默认版本: 2
### Distro Version
_No response_
### Other Software
docker desktop 4.73.0
### Repro Steps
Open wsl with Virtuproxy, docker desktop, access localhost::19011 will meet ERR_CONNECTION_RESET and will meet 503 error at not same LAN net machine test . But the NAT Net mode is fine.
### Expected Behavior
Virtuproxy should work properly.
### Actual Behavior
The NAT net mode wsl2 host not support IPv6 but docker desktop IPv6 settings is work fine.
> wsluser@Desktop:~$ ping -6 2603:1040:404:f::a
> ping: connect: Network is unreachable
### Diagnostic Logs
[WslLogs-2026-05-12_17-32-07.tar.gz](https://github.com/user-attachments/files/27630678/WslLogs-2026-05-12_17-32-07.tar.gz)
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.
Research direction
Start by reviewing the attached WslLogs-2026-05-12_17-32-07.tar.gz and reproducing the issue with WSL 2, Ubuntu 24.04, Docker Desktop 4.73.0, and VirtuioProxy. Compare localhost and public-IP container access in VirtuProxy mode with NAT mode, focusing on the reported IPv6 network-unreachable behavior. Done means container ports work through VirtuioProxy without connection resets or 503 errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100