<div dir="ltr">Hello,<div><br></div><div>I am trying to get a Centos VM working with Vagrant + VirtualBox on Windows 8. However I'm getting an error to do with the centos/7 box. </div><div><br></div><div>I have installed Vagrant using its automated installer, and VirtualBox, and downloaded this box:</div><div><br></div><div><a href="https://app.vagrantup.com/centos/boxes/7">https://app.vagrantup.com/centos/boxes/7</a></div><div><br></div><div>here is the output of that:</div><div><br></div><div><div>D:\Vagrant>vagrant box add centos/7</div><div>==> box: Loading metadata for box 'centos/7'</div><div> box: URL: <a href="https://vagrantcloud.com/centos/7">https://vagrantcloud.com/centos/7</a></div><div>This box can work with multiple providers! The providers that it</div><div>can work with are listed below. Please review the list and choose</div><div>the provider you will be working with.</div><div><br></div><div>1) hyperv</div><div>2) libvirt</div><div>3) virtualbox</div><div>4) vmware_desktop</div><div><br></div><div>Enter your choice: 3</div><div>==> box: Adding box 'centos/7' (v1801.02) for provider: virtualbox</div><div> box: Downloading: <a href="https://vagrantcloud.com/centos/boxes/7/versions/1801.02/providers/virtualbox.box">https://vagrantcloud.com/centos/boxes/7/versions/1801.02/providers/virtualbox.box</a></div><div> box: Progress: 100% (Rate: 950k/s, Estimated time remaining: --:--:--)</div><div>==> box: Successfully added box 'centos/7' (v1801.02) for 'virtualbox'!</div></div><div><br></div><div><br></div><div>So I did a vagrant init, ran "vagrant up" and I got a warning about VB guest additions needed, so I ran this command: </div><div><br></div><div>
<pre style="box-sizing:border-box;font-family:SFMono-Regular,Consolas,"Liberation Mono",Menlo,Courier,monospace;font-size:11.9px;margin-top:0px;margin-bottom:16px;word-wrap:normal;padding:16px;overflow:auto;line-height:1.45;background-color:rgb(246,248,250);border-radius:3px;color:rgb(36,41,46);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><code style="box-sizing:border-box;font-family:SFMono-Regular,Consolas,"Liberation Mono",Menlo,Courier,monospace;font-size:11.9px;padding:0px;margin:0px;background:transparent;border-radius:3px;word-break:normal;white-space:pre;border:0px;display:inline;overflow:visible;line-height:inherit;word-wrap:normal">vagrant plugin install vagrant-vbguest</code></pre><div><div>D:\Vagrant>vagrant plugin install vagrant-vbguest</div><div>Installing the 'vagrant-vbguest' plugin. This can take a few minutes...</div><div>Fetching: micromachine-2.0.0.gem (100%)</div><div>Fetching: vagrant-vbguest-0.15.1.gem (100%)</div><div>Installed the plugin 'vagrant-vbguest (0.15.1)'!</div></div><div><br></div>I then tried "vagrant up" again but got this error:</div><div><br></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Cannot find a valid baseurl for repo: base/7/x86_64</span>
<br></div><div><br></div><div>I don't know how to fix it. I append the error trace and my Vagrantfile. Any help will be appreciated.</div><div><br></div><div>thanks,</div><div><br></div><div>Simon</div><div><br></div><div>Appendages...</div><div><br></div><div><br></div><div>ERROR TRACE</div><div>=============</div><div><br></div><div><div>D:\Vagrant>vagrant up</div><div>Bringing machine 'default' up with 'virtualbox' provider...</div><div>==> default: Checking if box 'centos/7' is up to date...</div><div>==> default: Clearing any previously set forwarded ports...</div><div>==> default: Clearing any previously set network interfaces...</div><div>==> default: Preparing network interfaces based on configuration...</div><div> default: Adapter 1: nat</div><div>==> default: Forwarding ports...</div><div> default: 80 (guest) => 8080 (host) (adapter 1)</div><div> default: 22 (guest) => 2222 (host) (adapter 1)</div><div>==> default: Running 'pre-boot' VM customizations...</div><div>==> default: Booting VM...</div><div>==> default: Waiting for machine to boot. This may take a few minutes...</div><div> default: SSH address: <a href="http://127.0.0.1:2222">127.0.0.1:2222</a></div><div> default: SSH username: vagrant</div><div> default: SSH auth method: private key</div><div>==> default: Machine booted and ready!</div><div>[default] No installation found.</div><div>Loaded plugins: fastestmirror</div><div><br></div><div><br></div><div> One of the configured repositories failed (Unknown),</div><div> and yum doesn't have enough cached data to continue. At this point the only</div><div> safe thing yum can do is fail. There are a few ways to work "fix" this:</div><div><br></div><div> 1. Contact the upstream for the repository and get them to fix the problem.</div><div><br></div><div> 2. Reconfigure the baseurl/etc. for the repository, to point to a working</div><div> upstream. This is most often useful if you are using a newer</div><div> distribution release than is supported by the repository (and the</div><div> packages for the previous distribution release still work).</div><div><br></div><div> 3. Run the command with the repository temporarily disabled</div><div> yum --disablerepo=<repoid> ...</div><div><br></div><div> 4. Disable the repository permanently, so yum won't use it by default. Yum</div><div> will then just ignore the repository until you permanently enable it</div><div> again or use --enablerepo for temporary usage:</div><div><br></div><div> yum-config-manager --disable <repoid></div><div> or</div><div> subscription-manager repos --disable=<repoid></div><div><br></div><div> 5. Configure the failing repository to be skipped, if it is unavailable.</div><div> Note that yum will try to contact the repo. when it runs most commands,</div><div> so will have to try and fail each time (and thus. yum will be be much</div><div> slower). If it is a very temporary problem though, this is often a nice</div><div> compromise:</div><div><br></div><div> yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true</div><div><br></div><div>Cannot find a valid baseurl for repo: base/7/x86_64</div><div>==> default: Checking for guest additions in VM...</div><div> default: No guest additions were detected on the base box for this VM! Guest</div><div> default: additions are required for forwarded ports, shared folders, host only</div><div> default: networking, and more. If SSH fails on this machine, please install</div><div> default: the guest additions and repackage the box to continue.</div><div> default:</div><div> default: This is not an error message; everything may continue to work properly,</div><div> default: in which case you may ignore this message.</div><div>The following SSH command responded with a non-zero exit status.</div><div>Vagrant assumes that this means the command failed!</div><div><br></div><div>yum install -y kernel-devel-`uname -r` gcc binutils make perl bzip2</div><div><br></div><div>Stdout from the command:</div><div><br></div><div>Loaded plugins: fastestmirror</div><div><br></div><div><br></div><div>Stderr from the command:</div><div><br></div><div><br></div><div><br></div><div> One of the configured repositories failed (Unknown),</div><div> and yum doesn't have enough cached data to continue. At this point the only</div><div> safe thing yum can do is fail. There are a few ways to work "fix" this:</div><div><br></div><div> 1. Contact the upstream for the repository and get them to fix the problem.</div><div><br></div><div> 2. Reconfigure the baseurl/etc. for the repository, to point to a working</div><div> upstream. This is most often useful if you are using a newer</div><div> distribution release than is supported by the repository (and the</div><div> packages for the previous distribution release still work).</div><div><br></div><div> 3. Run the command with the repository temporarily disabled</div><div> yum --disablerepo=<repoid> ...</div><div><br></div><div> 4. Disable the repository permanently, so yum won't use it by default. Yum</div><div> will then just ignore the repository until you permanently enable it</div><div> again or use --enablerepo for temporary usage:</div><div><br></div><div> yum-config-manager --disable <repoid></div><div> or</div><div> subscription-manager repos --disable=<repoid></div><div><br></div><div> 5. Configure the failing repository to be skipped, if it is unavailable.</div><div> Note that yum will try to contact the repo. when it runs most commands,</div><div> so will have to try and fail each time (and thus. yum will be be much</div><div> slower). If it is a very temporary problem though, this is often a nice</div><div> compromise:</div><div><br></div><div> yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true</div><div><br></div><div>Cannot find a valid baseurl for repo: base/7/x86_64</div></div><div><br></div><div><br></div><div>MY VAGRANTILE</div><div>==============</div><div><br></div><div><div># -*- mode: ruby -*-</div><div># vi: set ft=ruby :</div><div><br></div><div># All Vagrant configuration is done below. The "2" in Vagrant.configure</div><div># configures the configuration version (we support older styles for</div><div># backwards compatibility). Please don't change it unless you know what</div><div># you're doing.</div><div>Vagrant.configure("2") do |config|</div><div> # The most common configuration options are documented and commented below.</div><div> # For a complete reference, please see the online documentation at</div><div> # <a href="https://docs.vagrantup.com">https://docs.vagrantup.com</a>.</div><div><br></div><div> # Every Vagrant development environment requires a box. You can search for</div><div> # boxes at <a href="https://vagrantcloud.com/search">https://vagrantcloud.com/search</a>.</div><div> config.vm.box = "centos/7"</div><div><br></div><div> # Disable automatic box update checking. If you disable this, then</div><div> # boxes will only be checked for updates when the user runs</div><div> # `vagrant box outdated`. This is not recommended.</div><div> # config.vm.box_check_update = false</div><div><br></div><div> # Create a forwarded port mapping which allows access to a specific port</div><div> # within the machine from a port on the host machine. In the example below,</div><div> # accessing "localhost:8080" will access port 80 on the guest machine.</div><div> # NOTE: This will enable public access to the opened port</div><div> # config.vm.network "forwarded_port", guest: 80, host: 8080</div><div><br></div><div> # Create a forwarded port mapping which allows access to a specific port</div><div> # within the machine from a port on the host machine and only allow access</div><div> # via 127.0.0.1 to disable public access</div><div> config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"</div><div><br></div><div> # Create a private network, which allows host-only access to the machine</div><div> # using a specific IP.</div><div> # config.vm.network "private_network", ip: "192.168.33.10"</div><div><br></div><div> # Create a public network, which generally matched to bridged network.</div><div> # Bridged networks make the machine appear as another physical device on</div><div> # your network.</div><div> # config.vm.network "public_network"</div><div><br></div><div> # Share an additional folder to the guest VM. The first argument is</div><div> # the path on the host to the actual folder. The second argument is</div><div> # the path on the guest to mount the folder. And the optional third</div><div> # argument is a set of non-required options.</div><div> # config.vm.synced_folder "./data", "/vagrant_data"</div><div><br></div><div> # Provider-specific configuration so you can fine-tune various</div><div> # backing providers for Vagrant. These expose provider-specific options.</div><div> # Example for VirtualBox:</div><div> #</div><div> config.vm.provider "virtualbox" do |vb|</div><div> # # Display the VirtualBox GUI when booting the machine</div><div> # vb.gui = true</div><div> #</div><div> # # Customize the amount of memory on the VM:</div><div> # vb.memory = "1024"</div><div> vb.customize ["modifyvm", :id, "--natdnshostresolver1", "off"]</div><div> end</div><div> #</div><div> # View the documentation for the provider you are using for more</div><div> # information on available options.</div><div><br></div><div> # Enable provisioning with a shell script. Additional provisioners such as</div><div> # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the</div><div> # documentation for more information about their specific syntax and use.</div><div> # config.vm.provision "shell", inline: <<-SHELL</div><div> # apt-get update</div><div> # apt-get install -y apache2</div><div> # SHELL</div><div> </div><div> config.vm.synced_folder ".", "/vagrant", type: "virtualbox"</div><div> </div><div>end</div></div><div><br></div></div>