docker-machine-driver-xhyve
docker-machine-driver-xhyve copied to clipboard
machine-drivers
Network routing not configured in xhyve VM
Thanks for this awesome project - I was able to really easily get an xhyve VM created, but I'm having trouble getting the guest connected to the Internet. Here's the network info:
https://gist.github.com/paulcbetts/44d3778e7392c20ae371
Anything I can do to troubleshoot this / debug sth?
+1
Networking info: https://gist.github.com/calle-gunnarsson/ba04e6d6a222e5fb26f0
Having the same issue.
Interestingly, I can do DNS resolution and ping from inside the VM just fine:
docker@boot2docker:~$ ping google.com
PING google.com (216.58.192.46): 56 data bytes
64 bytes from 216.58.192.46: seq=0 ttl=54 time=14.127 ms
^C
--- google.com ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 14.127/14.127/14.127 ms
But TCP connections hang:
docker@boot2docker:~$ nc -v google.com 80
^C
This behavior seems limited to ports 80 and 443. Other ports work just fine:
docker@boot2docker:~$ nc -v github.com 80
^C
docker@boot2docker:~$ nc -v github.com 22
github.com (192.30.252.129:22) open
SSH-2.0-libssh-0.7.0
^C
I can do DNS resolution, but nothing more, not ping, not nc on port 22 nor 80, I have IceFloor(pf frontend) installed on my mac, but I disabled it with the same result.
Having the same issue.
I'm wondering if it's to do with being the 3rd or 4th vm I've made with xhyve?
My network stats looks basically the same as @paulcbetts @calle-gunnarsson
Any progress on this. Just trying xhyve out tonight and apt-get update is failing, inspecting with netcat I too cannot hit port 80 on anything, it just returns 404.
root@fc41371499c7:/# nc google.com 80
GET http://google.com/ HTTP/1.1
HTTP/1.1 404 Not Found
Content-Type: text/html
Date: Fri, 22 Apr 2016 05:18:54 GMT
Connection: keep-alive
Transfer-Encoding: chunked
31
<!doctype html><html><body><h1>404 Not Found</h1>
0
@shayne If you're getting responses back, that seems like a different issue
For posterity's sake: Turns out this was most likely pow installed on the laptop. Not sure how this was interfering, but I figure it was intercepting requests due to its resolver. Uninstalled and no longer have the issue.
@paulcbetts and all I was resume maintenance this project.
Also, will debug that problem. Please wait a moment.
I get a similar problem. ping works, but dns doesn't resolve. I have dnsmasq installed, which I guess might be causing the problem based on the discussion of pow above.
