issue when running vagrant up --provider=virtualbox

[Jakub Sokołowski]

Hello,

I am invoking this command to start virtual box with vagrant

vagrant up --provider=virtualbox

and getting following error

ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Error, some other host already uses address 10.2.2.2.

I have a feeling that virtual box is blocking itself. Because when killing all virtual instances started by vagrant no one is occupying url 10.2.2.2.

Thanks for you help.

Best Regards, Jakub.

[Jakub Sokołowski]

Here is my Vagrantfile:

# -*- mode: ruby -*-
# vi: set ft=ruby :

VAGRANTFILE_API_VERSION = "2"
Vagrant.require_version ">= 1.7.2"

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version. Please don't change it unless you know what
# you're doing.
Vagrant.configure(2) do |config|

  config.vm.box = "thesteve0/openshift-origin"
  # uncomment this line if you downloaded the box and want to use it instead
  # config.vm.box = "openshift3"
  config.vm.box_check_update = false
  config.vm.network "private_network", ip: "10.2.2.2"
  config.vm.synced_folder ".", "/vagrant", disabled: true
  config.vm.hostname = "origin"


  # 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
  # config.vm.network "forwarded_port", guest: 80, host: 1080
  # config.vm.network "forwarded_port", guest: 443, host: 1443
  # config.vm.network "forwarded_port", guest: 5000, host: 5000
  # config.vm.network "forwarded_port", guest: 8080, host: 8080
  # config.vm.network "forwarded_port", guest: 8443, host: 8443

  config.vm.provider "virtualbox" do |vb|
     #   vb.gui = true
     vb.memory = "4096"
     vb.cpus = 2
     vb.name = "origin-1.3.0"
  end

end

[Alvaro Miranda Aguilera]

hello

the error is telling you tat that IP already exists.

comment out config.vm.network "private_network", ip: "10.2.2.2"

vagrant probabl does that for you already

if Virtualbox is using the network 10.2.2.x

then try a different network for your private_network

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/8f8eab05-005a-4782-ba66-5e0a148c9751%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro