unable to run multiple vagrant instances of ubuntu/xenial64 box

Bug #1567259 reported by LoOoD on 2016-04-07
This bug affects 20 people
Affects Status Importance Assigned to Milestone

Bug Description

I've got 2 seperate repos that use vagrant. Both are configured to use ubuntu/xenial64 box. Once I 'up' a vagrant from one repo, I can't run unbuntu/xenial64 box for the other.

$ vagrant up xenial
Bringing machine 'xenial' up with 'virtualbox' provider...
==> xenial: Importing base box 'ubuntu/xenial64'...
==> xenial: Matching MAC address for NAT networking...
==> xenial: Checking if box 'ubuntu/xenial64' is up to date...
A VirtualBox machine with the name 'ubuntu-xenial-16.04-cloudimg' already exists.
Please use another name or delete the machine with the existing
name, and try again.

The Vagrantfile INSIDE the virtualbox.box comes with some definitions that i guess shouldn't be there.

Here is the Vagrantfile from Trusty x Xenial

== Trusty ==

➜ boxes cat ubuntu-VAGRANTSLASH-trusty64/20160323.1.0/virtualbox/Vagrantfile
Vagrant::Config.run do |config|
  # This Vagrantfile is auto-generated by 'vagrant package' to contain
  # the MAC address of the box. Custom configuration should be placed in
  # the actual 'Vagrantfile' in this box.
  config.vm.base_mac = "0800278856E6"

# Load include vagrant file if it exists after the auto-generated
# so it can override any of the settings
include_vagrantfile = File.expand_path("../include/_Vagrantfile", __FILE__)
load include_vagrantfile if File.exist?(include_vagrantfile)

== Xenial ==
➜ boxes cat ubuntu-VAGRANTSLASH-xenial64/20160411.0.0/virtualbox/Vagrantfile
# Front load the includes
include_vagrantfile = File.expand_path("../include/_Vagrantfile", __FILE__)
load include_vagrantfile if File.exist?(include_vagrantfile)

Vagrant.configure("2") do |config|
  config.vm.base_mac = "020E47A5C995"
  config.ssh.username = "ubuntu"
  config.ssh.password = "7f63355c16f325d44b440caa"
  config.vm.synced_folder '.', '/vagrant', disabled: true

  config.vm.provider "virtualbox" do |vb|
     vb.name = "ubuntu-xenial-16.04-cloudimg"
     vb.customize [ "modifyvm", :id, "--uart1", "0x3F8", "4" ]
     vb.customize [ "modifyvm", :id, "--uartmode1", "file", File.join(Dir.pwd, "%s-console.log" % vb.name) ]

Tanmaya (tanmaya-8) wrote :

You can try adding this to your Vagrantfile for now:

     v.customize ["modifyvm", :id, "--name", "your-custom-name"]

Vladimir Rutsky (rutsky) wrote :

This issue also breaks Vagrant Multi-Machine configuration: https://www.vagrantup.com/docs/multi-machine/

Daniel brooks (bass-rock) wrote :

This box has a really invalid vagrant configuration. The username and password needs to change and it needs to follow the guidelines for being a vagrant box.

Michael Rooney (mrooney) wrote :

Seems confirmed via multiple bug reports on the Vagrant side including https://github.com/mitchellh/vagrant/issues/7389

Changed in cloud-images:
status: New → Confirmed
Patrik Karisch (patkar) wrote :

Can you simply remove the whole configure section from the Vagrantfile? Like the trusty box?

Patrik Karisch (patkar) wrote :

And of course, add the vagrant default insecure key to the authorized keys.

ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA6NF8iallvQVp22WDkTkyrtvp9eWW6A8YVr+kz4TjGYe7gHzIw+niNltGEFHzD8+v1I2YJ6oXevct1YeS0o9HZyN1Q9qgCgzUFtdOKLv6IedplqoPkcmF0aYet2PkEDo3MlTBckFXPITAMzF8dJSIFo9D8HfdOV0IAdx4O7PtixWKn5y2hMNG0zQPyUecp4pzC6kivAIhyfHilFR61RGL+GPXQ2MWZWFYbAGjyiYJnAmCP3NOTd0jMZEnDkbUvxhMmBYSdETk1rRgm+R4LOzFUGaHqHDLKLX+FIPKcF96hrucXzcWyLbIbEgE98OHlnVYCzRdK8jlqm8tehUc9c9WhQ== vagrant insecure public key

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.