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.

Sign up for GitHub

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

Jump to bottom

Docker/WSL2 support via IPv6 loopback #1074

Closed
jefflill opened this issue Nov 17, 2020 · 1 comment
Closed

Docker/WSL2 support via IPv6 loopback #1074

jefflill opened this issue Nov 17, 2020 · 1 comment
Assignees
@jefflill
Labels
bug Identifies a bug or other failure

Comments

@jefflill
Copy link
Collaborator

jefflill commented Nov 17, 2020 •
edited
Loading

We've disabled Docker/WSL2 integration on our workstations because WSL2 doesn't bind to the IPv4 loopback address 127.0.0.1 when a container app binds to 0.0.0.0. WSL2 does bind to the IPv6 loopback though as described in this issue:

microsoft/WSL#4983

The fix may be as easy as updating the unit text fixtures to use the localhost hostname instead of the IPv4 loopback address. This works because the DNS lookup for localhost returns [::1].

It would be nice to get this working because Docker on WSL2 is supposed to perform much better.
@jefflill jefflill added the investigate Needs further investigation label Nov 17, 2020
@jefflill jefflill self-assigned this Nov 17, 2020
jefflill added a commit that referenced this issue Nov 18, 2020
@jefflill
#1074: Docker/WSL2 support via IPv6 loopback
f6cf54a
@jefflill jefflill added bug Identifies a bug or other failure and removed investigate Needs further investigation labels Nov 18, 2020
@jefflill
Copy link
Collaborator Author

Fixed for neonLIBRARY v2.7.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jefflill jefflill

Labels
bug Identifies a bug or other failure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jefflill