whats your Vagrantfile ?
On Thu, Nov 17, 2016 at 11:55 PM, Jay Christopherson <[email protected]> wrote: > I'm trying to get a CoreOS cluster up and running to test out Nomad. But > for some reason, Vagrant keeps assigning a second interface IP to the > host-only interface, in the network 192.168.56.0/24: > > core@client-01 ~ $ ip addr show > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group > default qlen 1 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast > state UP group default qlen 1000 > link/ether 08:00:27:12:6f:56 brd ff:ff:ff:ff:ff:ff > inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic eth0 > valid_lft 86318sec preferred_lft 86318sec > inet6 fe80::a00:27ff:fe12:6f56/64 scope link > valid_lft forever preferred_lft forever > 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast > state UP group default qlen 1000 > link/ether 08:00:27:c8:4b:ef brd ff:ff:ff:ff:ff:ff > *inet 192.168.56.102/24 <http://192.168.56.102/24> brd 192.168.56.255 > scope global dynamic eth1* > valid_lft 1112sec preferred_lft 1112sec > inet 172.17.8.101/24 brd 172.17.8.255 scope global eth1 > valid_lft forever preferred_lft forever > inet6 fe80::a00:27ff:fec8:4bef/64 scope link > valid_lft forever preferred_lft forever > 4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue > state DOWN group default > link/ether 02:42:91:2c:1b:15 brd ff:ff:ff:ff:ff:ff > inet 172.18.0.1/16 scope global docker0 > valid_lft forever preferred_lft forever > > > DHCP has been disabled for that interface (VBoxManager) and that network > is not defined anywhere in my Vagrantfile. Does anyone know how that > network is being created and how I get rid of it (permanently)? It's > causing a bunch of problems with other tools, getting confused about which > interface IP to use. > > -- > 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 [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/vagrant-up/ff3dcb10-0bb6-408a-9913-37ec73015363%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/ff3dcb10-0bb6-408a-9913-37ec73015363%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Alvaro -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0exdd9j5NPWb6E2XbprBjgwTo3QCUjN6NP0FffdrcgcM0Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
