Re: vagrant - debiansid
I found the issue, but this is not resolved.....
I remind I tried to create a debian sid.
The default network interface name created (from recent udev it seems) is enp0s3, not eth0. In /etc/network/interfaces, there is a declaration for eth0, no ip address is bound via the DHCP.
The network config should match enp0s3 instead. If I manually update this and restart network, it is fine.
Now, I don't know where this should be managed (bootstrap-vz network, boostrap-vz virtualbox provider, ..?)
olivier sallou <firstname.lastname@example.org> writes:
> I tried to do so using bootstrap-vz, but there is failure at vagrant up, I
> can't connect, neither using vagrant insecure key nor using directly
> However, if I launch it directly via VirtualBox, I can use root login
> I wonder if it is not a VirtualBoxAdditions issue / port mapping,...
> during bootstrap-vz I see this error:
> The headers for the current running kernel were not found. If the following
> module compilation fails then this could be the reason.
> Building the main Guest Additions module ...fail!
> (Look at /var/log/vboxadd-install.log to find out what went wrong)
> Doing non-kernel setup of the Guest Additions ...done.
> Installing the Window System drivers
> Could not find the X.Org or XFree86 Window System, skipping.
> It seems that bootstrap-vz with VirtualBox does not add automatically the
> linux kernel headers package to compile additions, nor X packages (but this
> is not the issue here).
Yes, there are/were issues about the kernel header versions between host
> I have no issue with other "base" boxes (Debian, CentOS, ..) using vagrant.
Which version of bootstrap-vz did you use ?
I remember we once needed the version from the development branch in
Then it seems the master branch was working at some point, since I
changed this :
A recent one, but don't know which one. I gonna retry using latest from master.