Actually, that's NOT the case - networking is one section in vagrant where
it builds up from the base package, then subsequent Vagrantfile's,
appending to the configuration, not overriding. From
: https://www.vagrantup.com/docs/vagrantfile/
> However, for things such as defining networks, the
Hello, on vagrant up, vagrant will clear the networking of the box and set
whats on the Vagrantfile.
seems i miss understood the issue, sorry.
IF you still have the base box, can you share a `ifconfig -a` as root ?
On Mon, May 30, 2016 at 4:00 PM, BRIT
- vagrant version 1.8.1
- vagrant-share (1.1.5, system)
Log file is attached. Editing the file with the private network worked
just fine. This hasn't been the issue. The issue is that when I create a
base box, there's an additional NIC that's obtaining DHCP settings from
On Tue, May 31, 2016 at 10:07 AM, BRIT <
buildingreliableitsoluti...@gmail.com> wrote:
> for cmd.exe
> set VAGRANT_LOG=debug
>
> for bash
> export VAGRANT_LOG=debug
>
> then:
>
> vagrant up
>
> And share the generated text over a gist. (gist.github.com)
Hello, are you installing Vagrant from
the "curl -L ..." worked just fine. Oddly enough, I went through and
reinstalled both vagrant and virtualbox before reading your post Alvaro.
One thing I do notice, working on my Ubuntu desktop: there are two ways of
loading VirtualBox, with differing results:
1. Dash > Applications >
Hello,
Are you behind any firewall or proxy that may be stopping this to work?
Or do you need to define a proxy?
Please try this:
curl -L https://atlas.hashicorp.com/cbednarski/ubuntu-1404.json
If that works, then I would suggest reinstall vagrant on that machine.
If after reinstall the issue