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

vagrant.sh hangs #31

Open
asimpletune opened this issue Mar 20, 2015 · 5 comments
Open

vagrant.sh hangs #31

asimpletune opened this issue Mar 20, 2015 · 5 comments

Comments

@asimpletune
Copy link

I'm not sure what exactly is wrong, but vagrant.sh always hangs at the curl command, where it gets the weak key from hashicorp. Even copying the key locally and echoing it to authorized doesn't work, so I'm sure it's something else that I'm doing wrong.

This is for OS X 10.10

Thanks!

@timsutton
Copy link
Owner

Does that same script run ok when run locally on your host? I'm just wondering if there's an issue with either your host or the way in which it's configured VMware's NAT. This would be the first time that your guest tries to reach out to the internet.

We should probably pass curl a timeout option so that at least the run will fail early.

@asimpletune
Copy link
Author

I should have mentioned that the builder I"m using is virtualbox-iso, not vmware.

No, it doesn't work on my host, but for different reasons. Since the VM is nat'd to my host, this should work if my host doesn't have any issue connecting to the interent.

@asimpletune
Copy link
Author

Hey Tim, so an update on this. For this specific issue, disconnecting from VPN seemed to resolve the problem of the script just hanging.

@timsutton
Copy link
Owner

So is it safe to say this looks like an issue with either your specific environment, or the way VirtualBox is handling outbound connections when your VPN client has established a connection? I've never tested running a build over VPN, and wouldn't necessarily expect VM NAT'ing to work through all that, or at least in the same way across different VM providers.

@asimpletune
Copy link
Author

Turns out VPN is wrong and I was observing a separate issue, that I'll have to revisit in the future.

To answer your question though, VirtualBox consumes whatever is present in your environment, so it would be more likely to be the environment than VirtualBox. Sometimes, VPN software will change things that'll add a touch of strangeness to your internal networking, like how boot2docker can't communicate to the docker daemon unless you communicate directly through the boot2docker VM's ip, rather than localhost. But I don't know enough about it to really say more than that, just something I've observed.

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

2 participants