I started a container with a port running on 3000, I used
docker run -p 3000:3000, and I can access it from my OSX terminal by getting
docker-machine ip and then hitting it with curl:
$ curl --silent http://192.168.99.100:3000 | head <html> <head> <title>myapp</title> ...
I can load it in Safari too.
It doesn’t load in Chrome. I can’t figure out why. I tried using an Incognito Window (to ensure it isn’t an extension I’m using), I checked to see if there was a proxy (nope), my VPN is turned off,
netstat -nrf inet shows the entry:
192.168.99.100 8:0:27:5f:b:61 UHLWIi 3 276768 vboxnet 1178
So… why would it fail in Chrome? I’m hoping someone else has run into this.
I also note I don’t have a docker.local or anything else in my
resolv.conf; I don’t know if that’s true in the modern Docker for Mac world (1.12-beta21). The “diagnose & feedback” screen shows that everything is
[OK]. (oh, and 10.11.6)
- the output of:
Moby Menu > Diagnose & Feedbackon OSX
- a reproducible case if this is a bug, Dockerfiles FTW
- page URL if this is a docs issue or the name of a man page
- host distribution and version ( OSX 10.10.x, OSX 10.11.x, Windows, etc )
Steps to reproduce the behavior