--net=host an anti-pattern on "native" Docker for OS X

[rgbkrk]

See https://forums.docker.com/t/should-docker-run-net-host-work/14215

We need to expose the port for the proxy directly while having access to the rest of the containers.

[cloutiertyler]

I'm just going to mention macOS here for anyone trying to search that instead of OS X.

Edit: Incidentally, do you know of any work arounds for running on macOS? I'm unable to get the ip address of the Docker for Mac VM (docker-machine ls, seems to no longer work for Mac).

[cloutiertyler]

It looks like this was fixed in #258, no?

I'm still riding the struggle bus however. Getting a whole bunch of this on start up.

tmpnb_1        | [W 170824 23:58:17 spawnpool:330] Socket error on boot: [Errno 111] Connection refused
tmpnb_1        | [W 170824 23:58:17 spawnpool:330] Socket error on boot: [Errno 111] Connection refused
tmpnb_1        | [W 170824 23:58:17 spawnpool:330] Socket error on boot: [Errno 111] Connection refused
tmpnb_1        | [W 170824 23:58:17 spawnpool:330] Socket error on boot: [Errno 111] Connection refused
tmpnb_1        | [W 170824 23:58:17 spawnpool:330] Socket error on boot: [Errno 111] Connection refused
tmpnb_1        | [W 170824 23:58:17 spawnpool:330] Socket error on boot: [Errno 111] Connection refused```