Unable to communicate from inside container to the host through the 192.168.65.1 IP
galenus opened this issue · comments
Expected behavior
Containers could reach the host machine through the 192.168.65.1
The same woks in versions 17.09.*, rolling back fixes this problem.
Actual behavior
Connection to the host times out.
Information
- Version: 17.12.0-ce-win47 (15139)
- Channel: stable
- Sha1: 9c692cd5b38166289573183371647d915f300292
- Started on: 2018-01-31 08:43:19.936
- Resources: C:\Program Files\Docker\Docker\Resources
- OS: Windows 10 Enterprise
- Edition: Enterprise
- Id: 1709
- Build: 16299
- BuildLabName: 16299.15.amd64fre.rs3_release.170928-1534
Steps to reproduce the behavior
- Execute the following command:
docker run -d -p 8080:8080 -v <location of the downloaded hello-on-port.js file>:/scripts node:alpine node /scripts/hello-on-port.js
- Launch additional container:
docker run -ti --rm alpine:latest
Inside the container:
apk add --update curl
curl 192.168.65.1:8080
- There is no response from the host, the only related lines from the log are like the following:
[09:39:03.646][VpnKit ][Info ] vpnkit.exe: Connected Ethernet interface f6:16:36:bc:f9:c6
[09:39:03.647][VpnKit ][Info ] vpnkit.exe: UDP interface connected on 192.168.65.1
IP is subject to changes. Please now use the docker.for.win.host.internal name to connect to the host from a container.
docker run alpine ping docker.for.win.host.internal
PING docker.for.win.host.internal (192.168.65.2): 56 data bytes
64 bytes from 192.168.65.2: seq=0 ttl=37 time=0.675 ms
64 bytes from 192.168.65.2: seq=1 ttl=37 time=0.374 ms
Thanks, I will try and report my findings
Yes, it works as expected. Closing the issue.
Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.
If you have found a problem that seems similar to this, please open a new issue.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked