Vagrant up command fails with "Could not resolve host: (nil); Host not found" error

[Amit Schnitzer]

C:\vagrant>vagrant up

Bringing machine 'default' up with 'virtualbox' provider...

[default] Box 'precise32' was not found. Fetching box from specified URL for

the provider 'virtualbox'. Note that if the URL does not have

a box for this provider, you should interrupt Vagrant now and add

the box yourself. Otherwise Vagrant will attempt to download the

full box prior to discovering this error.

Downloading or copying the box...

←[0KAn error occurred while downloading the remote file. The error--)

message, if any, is reproduced below. Please fix this error and try

again.

Could not resolve host: (nil); Host not found

[Terrance Shepherd]

What does your vagrant file look like?

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Amit Schnitzer]

I haven't changed the default one (the one that was created automatically with the "init" command)

[Terrance Shepherd]

could you post it for review and maybe include a debug log

[Amit Schnitzer]

Strangely enough, I now get a different error message "failed writing body"

my vagrant file 

# -*- mode: ruby -*-

# vi: set ft=ruby :

Vagrant.configure("2") do |config|

  # All Vagrant configuration is done here. The most common configuration

  # options are documented and commented below. For a complete reference,

  # please see the online documentation at vagrantup.com.

  # Every Vagrant virtual environment requires a box to build off of.

  config.vm.box = "precise32"

  # The url from where the 'config.vm.box' box will be fetched if it

  # doesn't already exist on the user's system.

  config.vm.box_url = "http://files.vagrantup.com/precise32.box"

  # Create a forwarded port mapping which allows access to a specific port

  # within the machine from a port on the host machine. In the example below,

  # accessing "localhost:8080" will access port 80 on the guest machine.

  config.vm.network :forwarded_port, guest: 80, host: 8080

  # Create a private network, which allows host-only access to the machine

  # using a specific IP.

  config.vm.network :private_network, ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.

  # Bridged networks make the machine appear as another physical device on

  # your network.

  config.vm.network :public_network

  # Share an additional folder to the guest VM. The first argument is

  # the path on the host to the actual folder. The second argument is

  # the path on the guest to mount the folder. And the optional third

  # argument is a set of non-required options.

  # config.vm.synced_folder "../data", "/vagrant_data"

  # Provider-specific configuration so you can fine-tune various

  # backing providers for Vagrant. These expose provider-specific options.

  # Example for VirtualBox:

  #

  # config.vm.provider :virtualbox do |vb|

  #   # Don't boot with headless mode

  #   vb.gui = true

  #

  #   # Use VBoxManage to customize the VM. For example to change memory:

  #   vb.customize ["modifyvm", :id, "--memory", "1024"]

  # end

  #

  # View the documentation for the provider you're using for more

  # information on available options.

  # Enable provisioning with Puppet stand alone.  Puppet manifests

  # are contained in a directory path relative to this Vagrantfile.

  # You will need to create the manifests directory and a manifest in

  # the file Precise32.pp in the manifests_path directory.

  #

  # An example Puppet manifest to provision the message of the day:

  #

  # # group { "puppet":

  # #   ensure => "present",

  # # }

  # #

  # # File { owner => 0, group => 0, mode => 0644 }

  # #

  # # file { '/etc/motd':

  # #   content => "Welcome to your Vagrant-built virtual machine!

  # #               Managed by Puppet.\n"

  # # }

  #

  # config.vm.provision :puppet do |puppet|

  #   puppet.manifests_path = "manifests"

  #   puppet.manifest_file  = "init.pp"

  # end

  # Enable provisioning with chef solo, specifying a cookbooks path, roles

  # path, and data_bags path (all relative to this Vagrantfile), and adding

  # some recipes and/or roles.

  #

  # config.vm.provision :chef_solo do |chef|

  #   chef.cookbooks_path = "../my-recipes/cookbooks"

  #   chef.roles_path = "../my-recipes/roles"

  #   chef.data_bags_path = "../my-recipes/data_bags"

  #   chef.add_recipe "mysql"

  #   chef.add_role "web"

  #

  #   # You may also specify custom JSON attributes:

  #   chef.json = { :mysql_password => "foo" }

  # end

  # Enable provisioning with chef server, specifying the chef server URL,

  # and the path to the validation key (relative to this Vagrantfile).

  #

  # The Opscode Platform uses HTTPS. Substitute your organization for

  # ORGNAME in the URL and validation key.

  #

  # If you have your own Chef Server, use the appropriate URL, which may be

  # HTTP instead of HTTPS depending on your configuration. Also change the

  # validation key to validation.pem.

  #

  # config.vm.provision :chef_client do |chef|

  #   chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"

  #   chef.validation_key_path = "ORGNAME-validator.pem"

  # end

  #

  # If you're using the Opscode platform, your validator client is

  # ORGNAME-validator, replacing ORGNAME with your organization name.

  #

  # If you have your own Chef Server, the default validation client name is

  # chef-validator, unless you changed the configuration.

  #

  #   chef.validation_client_name = "ORGNAME-validator"

end

[David Holt]

Was there ever an answer to this issue? I'm getting the same error. Has the location of the precise32 box changed? I'm getting nothing if I try to ping files.vagrantup.com.

[David Holt]

Never mind. I mistyped the url in the vagrant init command. Doh!

[Bhavesh Patel]

Yes, I am also getting the same error...

https://wiki.dlib.indiana.edu/pages/viewpage.action?pageId=515278422  Into this I have execute the command vagrant up then it's shows the following image.

I have also Install the Virtual Box and CentOS minimal on Virtual Box.

Please let us know if anyone knows this issue.

Thanks,

Bhavesh Patel

[Prajna]

Hello,

Did anyone get an answer to this issue? I still get the same error. 

I followed the instruction from http://docs.vagrantup.com/v2/getting-started/

Executed the below 2 commands 

vagrant init hashicorp/precise32

vagrant up

Below is the error message. 

************************************************************************************************************************************

C:\Users\xyz123>vagrant up

Bringing machine 'default' up with 'virtualbox' provider...

==> default: Box 'ubuntu/trusty32' could not be found. Attempting to find and in

stall...

    default: Box Provider: virtualbox

    default: Box Version: >= 0

The box 'ubuntu/trusty32' could not be found or

could not be accessed in the remote catalog. If this is a private

box on HashiCorp's Atlas, please verify you're logged in via

`vagrant login`. Also, please double-check the name. The expanded

URL and error message are shown below:

URL: ["https://atlas.hashicorp.com/ubuntu/trusty32"]

Error: Could not resolve host: (nil); Host not found

************************************************************************************************************************************

All the help appreciated

[Alvaro Miranda Aguilera]

On Thu, May 28, 2015 at 9:05 PM, Prajna <prajna...@gmail.com> wrote:
> 'ubuntu/trusty32'

Hello,

this box:

'ubuntu/trusty32'

it does exist.

The error you are getting is that vagrant is not able to reach
atlas.hashicorp.com

That seems to be some sort of network or dns problem.

Does your command line environment have a working internet?

Can you ping atlas.hashicorp.com
can you curl https://atlas.hashicorp.com/ubuntu/boxes/trusty32.json

If you have a proxy at work, you need to set up:

export http_proxy=http://proxy_server:proxy_port
and
export https_proxy=http://proxy_server:proxy_port

Thanks,
Alvaro

[Kanishka Vedi]

Thanks, its working after setting up the proxy.