Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dinghy cannot work when connect through Cisco VPN #287

Open
pkouda-ith opened this issue May 1, 2019 · 4 comments
Open

Dinghy cannot work when connect through Cisco VPN #287

pkouda-ith opened this issue May 1, 2019 · 4 comments

Comments

@pkouda-ith
Copy link

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
Copy link
Owner

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
Copy link

jimsimon commented Jul 3, 2019

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
Copy link
Owner

@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
Copy link

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants