Re: [vagrant-up] Private IP Assigned to Wrong NIC

I've copied the contents to https://github.com/hashicorp/vagrant/issues/9546, so go ahead and delete my comments. I'll try to get a repro case together. On Thu, Mar 8, 2018 at 1:03 PM, Alvaro Miranda Aguilera wrote: > not sure if the same > > please open a new issue, include

Re: [vagrant-up] Private IP Assigned to Wrong NIC

not sure if the same please open a new issue, include a repro case and instructions how to repro please @kikitux so i can get the notification to look into if happens to you and more people, should happen to us if you are ok, i would like to the delete the comment in that issue in 9510 since

[vagrant-up] Private IP Assigned to Wrong NIC

I'm having big problems with Vagrant lately: - My private network's IP gets properly assigned (to eth1) on the first vagrant up - On the first vagrant reload, the IP is inappropriately assigned to eth0 (the regular NAT network nic), and the IP now shows on both eth0 and eth1 -

Re: [vagrant-up] Enabling/Disabling plugins

hello it seems packer is a better tool for this, you can use virtualbox-ovf to start from an existing box have a look here: https://github.com/kikitux/virtualbox-ovf however, if you really want to use vagrant, you can use a shell provisioner to do the virtualbox part, so you keep all under

[vagrant-up] Enabling/Disabling plugins

Hi all, I'm looking at creating a Vagrant VM using a CI server with no internet connection. Or rather, the CI only has a connection to the internet via Artifactory, which is acting as a proxy for Yum packages and Vagrant boxes, including caching those files for reproducibility. I'm trying to