when creating a new box with "vagrant up" it always wants to add a new Host-Only adapter to virtual box

24 views
Skip to first unread message

Ted Coursen

unread,
Sep 21, 2018, 12:23:54 PM9/21/18
to Vagrant
I had a working configuration that had been working for a few months, but is now broken.

I am using Windows 10.  I am trying to create a VirtualBox  vm of Ubuntu with MongoDB running on it.

In my Vagrantfile I have the following line :

config.vm.network 'private_network', ip: "192.168.2.2"

When I run "vagrant up" from my command line it creates the VM, but it asks me twice for my windows admin credentials and then proceeds.   But then when I look in my Virtual Box settings I have a new host only adapter.  After running a few times I now have like 10 Host Only adapters in virtualbox.


Any ideas on what is happening here?

Alvaro Miranda Aguilera

unread,
Sep 25, 2018, 5:58:38 AM9/25/18
to vagra...@googlegroups.com
what version are you using now?

on what version did worked?

what did change?


--
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/585fa064-88d0-473e-bce3-49225a91d5cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
Alvaro

Ted Coursen

unread,
Oct 2, 2018, 9:54:55 AM10/2/18
to Vagrant
Windows 10
Using Vagrant 2.1.5
VirtualBox 5.2.18

Nothing changed in the Vagrantfile so I'm not sure what changed.   It had been working fine for months.    I usually end up deleting and rebuilding the vm every couple of weeks, so one time I deleted the Vm and did a new "vagrant up" and this started happening.

Oddly, if I use the same set of scripts on a linux mint machine, it works totally as expected and does not add an extra host adapter.
Reply all
Reply to author
Forward
0 new messages