search

codekitchen / dinghy

faster, friendlier Docker on OS X
MIT License
2.12k stars 109 forks source link

Dinghy cannot work when connect through Cisco VPN #287

Open pkouda-ith opened 5 years ago

pkouda-ith commented 5 years ago

Dinghy works fine when I am working with VPN. But once I connect to VPN through Cisco VPN, dinghy is not available and does not work as expected. All the Images are present in repos accessible through VPN only. Please suggest any workaround

codekitchen commented 5 years ago

Hi, can you provide more information on "dinghy is not available and does not work as expected"? What is not working, what are the symptoms, do you have any relevant log or console output?

I don't use Cisco VPN myself, so I really don't have any way to know what exactly is going wrong, I'll need a lot more detail. Thanks.

jimsimon commented 5 years ago

I'm running into this issue when attempting to use dinghy + xhyve + our Cisco AnyConnect VPN. When I'm connected to the VPN, I get the following log output from docker:

Building work
Step 1/18 : FROM instructure/ruby-passenger:2.5
ERROR: Service 'work' failed to build: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

This issue appears to be specific to using xhyve, as vbox works without issue. Everything seems to start working again if I disconnect from the VPN and restart dinghy. Just disconnecting from the VPN isn't enough, I have to restart dinghy as well. I've tried both connecting to the VPN before starting dinghy and connecting to the VPN after starting dinghy, and neither approach works.

codekitchen commented 5 years ago

@jimsimon That sounds like a docker-machine-driver-xhyve issue that I'm not going to be able to do anything about on the Dinghy side. Looking through that project I see this issue that talks about OpenVPN but sounds like it may be the same underlying problem. Maybe try that fix script? It does seem like the xhyve driver could probably do something to add that routing rule automatically, though.

AlbertoBarba commented 4 years ago

@jimsimon probably it's because the docker-machine network it's not allowed to use the vpn interfaces. I had a similar issue and i fixed it with this script https://gist.github.com/mowings/633a16372fb30ee652336c8417091222