Re: vagrant - debiansid

Le ven. 14 août 2015 à 13:52, olivier sallou <olivier.sallou@gmail.com> a écrit :

Le mer. 12 août 2015 à 13:17, Olivier Berger <olivier.berger@telecom-sudparis.eu> a écrit :
Hi.

olivier sallou <olivier.sallou@gmail.com> writes:

> Hi,
> does anyone use Vagrant with a Debian sid for packaging ?

Not me.

> If yes, do you have an url to specify in Vagrant?
>

You mean a base box ?

> I only see Debian releases, no testing/sid. I could of course update
> one, but I could use directly one as a base box....
>
> Even better, would be a Debian development box (with quilt,
> git-buildpackage etc... already installed etc...) would be a nice
> thing for DD/DMs.
>

I would advise not to use pre-made base boxes and instead to perform
your own builds, so that to avoid side effects or even worse, security
issues (MITM, etc.).

Last time I did some work with Vagrant for producing a Debian VM, I used
bootstrat-vz. See more details at
https://github.com/olberger/DebianJessieBaseBox (and about the VM, in
french, at :
https://fusionforge.int-evry.fr/plugins/scmgit/cgi-bin/gitweb.cgi?p=moocbdvm/moocbdvm.git;a=tree;f=VagrantBox;h=79c8e3071a4b2d0cdab321e00b019992ef26d66a;hb=HEAD )

Hope this helps.
Hi,
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 login/password.

However, if I launch it directly via VirtualBox, I can use root login successfully.

It seems that no network interface other than loopback is created. (so no network access from outside the VM). I see nothing however in bootstrap-vz manifest for this. I don't know if this has something to do with generated image or vagrant directly.

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).

I have no issue with other "base" boxes (Debian, CentOS, ..) using vagrant.

See you at DebConf.

Olivier

Best regards,

P.S.: we can discuss that in more details next week at DebConf ;)
--
Olivier BERGER
http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)