Skip to content
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

No tcp access from windows host to services running in WSL2/Ubuntu Docker-CE containers #12052

Closed
1 of 2 tasks
svenczbg opened this issue Sep 18, 2024 · 3 comments
Closed
1 of 2 tasks

Comments

@svenczbg
Copy link

Windows Version

Microsoft Windows 11 Enterprise 10.0.22631

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu 22.04.02 LTS

Other Software

Docker-CE 24.0.7-ubuntu~22.04.1

Repro Steps

  • Install Windows 365 Cloud PC (Windows 11, 2 vCPUs, 8 GB RAM, 128 GB Storage)
    • wsl --install from admin-powershell
  • in Ubuntu shell: sudo apt install docker.io -y
  • init docker swarm --advertise-addr
  • start a docker stack with several services
  • stack starts, all images loaded from docker hub and other registries
  • ping from host to ubuntu and back works
  • no access from host to services in wsl

After trying all recipes that google found, I tried to downgrade the Ubuntu to WSL1. Then I upgraded it back to WSL2. After that, I was able to connect to services in WSL/Ubuntu from the host.

Expected Behavior

Access to services within WSL/Ubuntu should work out of the box.

Actual Behavior

After installation of WSL2/Ubuntu & Docker, I had to downgrade to WSL1 and back up to WSL2 to get access from host to services in WSL/Ubuntu

Diagnostic Logs

Please let me know which log would be helpful. I can provide you with a cloud pc for testing.

Copy link

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

View similar issues

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!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@unclemusclez
Copy link

Feel free to tell us where the WSL2 Docker logs are.

Copy link
Contributor

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants