Latest OS X, non-beta, new MacBook Pro q4 2015. My company uses sshuttle to vpn from local dev to staging. Installing docker beta breaks that. I’m not an expert in OS X networking, but I couldn’t find any entries in the routing tables. The CiDR is 10.0.0.0/8, if that makes a difference. The problem goes away after disabling docker on boot and restarting. It would be cool if it did not do this. Otherwise it looked pretty good. Thanks!
I’m having some related troubles too, though I’m relatively new to sshuttle. Abstractly, the sequence looks like this:
host$ sshuttle --dns -r bastion.example.com 10.0.0.0/8 # meanwhile: host$ docker run --rm -it ubuntu:16.04 bash container$ curl http://internal.example.com/ # fails; but, with the container still running, host$ killall sshuttle host$ shuttle --dns -r bastion.example.com 10.0.0.0/8 container$ curl http://internal.example.com/ # works! container$ exit # just for fun, host$ docker run --rm -it ubuntu:16.04 bash container$ curl http://internal.example.com/ # works! container$ exit # Well, I got it working, so host$ make -f Makefile.big-and-runs-containers # time passes # ... # and the make fails host$ docker run --rm ubuntu:16.04 curl http://internal.example.com/ # also fails, again
I’d guess the “make” step takes maybe 30-60 seconds to fail; I don’t remember if the number of
docker run steps in it is more like “exactly 1” or “about a dozen”, but it is the first time it reaches into the private network.