-
Notifications
You must be signed in to change notification settings - Fork 168
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
Could not resolve host errors during vagrant up on yum install #91
Comments
Sorry for answering so late. I'm not sure what's happening in your case, and unfortunately I can't reproduce it on OS X:
If it still happens on your side, could you please include calls to debug networking in your shell provisioning? Something like |
I have update vagrant to 1.9.3 and centos/7 box to 1702.01 but still the same issue.
As you can see above, some of the first attempts to download packages fail and after a few minutes it all goes fine. This is the output of
also I noticed that |
It's worth noting that there is no such issue with centos/6 vagrant box, so I had to switch to it. |
Perhaps your local network doesn't work properly with IPv6. Could you manually add It might also be an old, but unfixed, VirtualBox bug affecting Windows users with IPv6 - over wireless, if I understand correctly (I just skimmed the messages). You could try connecting with a network cable, if you're on wireless. Another idea would be to configure VirtualBox to provide a DNS proxy. https://www.vagrantup.com/docs/virtualbox/configuration.html#gui-vs-headless |
I tried to connect with a cable and set ipv6.disable=1. It didn't help. Also I have |
Nothing changed from the perspective of the Vagrant images, and I can't reproduce it here on macOS (our automated tests would catch that on a CentOS 7 host, too - it might be Windows-specific, although we have reports that VMware works properly). But v1611.01 was the first release based on CentOS Linux 7.3.1611 (the previous ones were using packages from 7.2.1511). Perhaps the problem is upstream. Try asking in #centos on IRC, there are very knowledgeable people there who can help. Sorry, no idea what could be going on there. https://seven.centos.org/2016/12/updated-centos-vagrant-images-available-v1611-01/ |
Hi, I can confirm that we have the same errors with Windows 10 Enterprise, VB Version 5.1.14 r112924 (Qt5.6.2) and Vagrant 1.8.7. |
Did you try using Google's public DNS servers instead of the local ones? You could follow these steps:
I'm curious if this solves the problem you're seeing. Unfortunately, I don't have any Windows machine to try it on, and I don't see any problems on macOS. |
Hi, I solved my problem by doing those steps: Vagrant 1.9.3 install |
I've also run into this. I believe it is windows specific if that helps. I have a development environment I wrote and it is used by devs on windows,linux and mac. Only ones that ever have this problem are using windows. |
Now I can say for sure, that the issue can be observed on Windows with Same issue is not observed with |
@dhampik I just tried with the NAT DNS host resolver active, using your configuration line, and everything works fine on my Mac Mini (on OS X). Perhaps |
I have had the same issue, must set
Environment: Vagrant box: centos/7 v1710.01 |
Run this. |
Environment:
Windows 10 Home Edition
VirtualBox 5.0.30 (also tested with 5.0.32)
Vagrant 1.9.0 (also tested with 1.8.6)
Vagrant box: centos/7 v1611.01
Also tested with and without the following plugins:
vagrant-vbguest
(to install GuestAdditions) andvagrant-sshfs
During vagrant up I'm getting multiple
Could not resolve host
errors whenyum install
is performed. Basically it cannot resolve mirrors, but if I log in to the box after vagrant up, all hosts are resolvable.With my custom provisioning shell scripts I was managed to resolve it by putting
sleep 60
in the beginning of provisioning shell script (so it looks like some service is not working properly for the first few minutes after vagrant up), but I cannot do that forvagrant-vbguest
orvagrant-sshfs
and that causes failure.It is always reproducible, but I was not able to find any info about similar issues.
Important thing to note, that there is no such issue with vagrant box centos/7 v1610.01 (previous version), but I cannot use it due to missing kernel headers which vagrant-vbguest plugin cannot install (that is a known issue, I guess)
The text was updated successfully, but these errors were encountered: