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

Unable to communicate from inside container to the host through the 192.168.65.1 IP #1638

Closed
galenus opened this issue Jan 31, 2018 · 4 comments

Comments

@galenus
Copy link

galenus commented Jan 31, 2018

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

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

hello-on-port.zip

  1. Launch additional container:
docker run -ti --rm alpine:latest

Inside the container:

apk add --update curl
curl 192.168.65.1:8080
  1. 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

@pgayvallet
Copy link

pgayvallet commented Jan 31, 2018

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

@galenus
Copy link
Author

galenus commented Jan 31, 2018

Thanks, I will try and report my findings

@galenus
Copy link
Author

galenus commented Jan 31, 2018

Yes, it works as expected. Closing the issue.

@galenus galenus closed this as completed Jan 31, 2018
@docker-robott
Copy link
Collaborator

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

@docker docker locked and limited conversation to collaborators Jun 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants