-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
NAT DNS Proxy Option? #1234
Comments
I don't quite understand why this is happening and maybe the NAT DNS proxy is in fact NOT a sane default. Anyways, I've made a change to allow disabling this. More here: #1313 |
Ah, the god tier issue that is referenced by everyone that is too lazy to remove the template portions in their issue. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
I've spent a few days trying to isolate the cause of really bad instability (I'd only get through the whole up process, including chef provisioning, a fraction of the time) with a Win 7 x64 host and Ubuntu 12.04 32-bit guest. I finally got it down to the NAT DNS proxy option in the sane defaults.
Basically the host Ubuntu would run for a while then crash hard before finishing the bootstrapping process. I noticed it was usually associated with network transfers (i.e. lots of apt-gets in Chef). I checked out #909 (but it seems like that discussion had more to do with Ubuntu 12.04 hosts?). Finally I ended up manually turning off --natdnsproxy1 in my Vagrantfile, and suddenly everything's humming along fine.
I'm wondering if anyone has any more insight into why this was happening, and also to raise the question of whether there should be an option in the Vagrant config object to turn it off.
The text was updated successfully, but these errors were encountered: