[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#865269: cloud.debian.org: Please provide an official contrib-stretch64 vagrant base box



On 07/26/2017 01:45 PM, Lucas Nussbaum wrote:
> Hi,
> 
> On 21/06/17 at 17:00 +0200, Emmanuel Kasper wrote:
>>> Debian has provided official vagrant base boxes in 2 flavors - one without the VirtualBox guest additions
>>> and the other with the guest additions, since the Jessie release. With Stretch released a few days back,
>>> only the base box without the guest additions is available. Please provide a contrib-stretch64 base box
>>> with the guest additions.
>>
>> Thank your for your interest for the Vagrant Box with guest additions.
>>
>> The thing is that VirtualBox itself was removed from Stretch (but still
>> available in unstable) at the request of the package maintainer, due to
>> the difficulty of providing security fixes for stable releases.
>> ( see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794466 )
>>
>> This means it is not possible to install the guest additions on a
>> Stretch VM without first backporting the guest additions from unstable.
>> IIRC using the non-free iso containing the guest additions bring another
>> problem, is that the guest additions does not build inside the VM if the
>> VM itself is not running inside Virtualbox. But we build the VMs using qemu.
> 
> What is the reason for not using VirtualBox to build the images? Is that
> because of the need of a solution that can run inside another VM?

yes that would be a technical reason
but the main reason here is that VirtualBox is not free due to the
obscure license of the compiler required to build its bios (ggole
openwatcom license)

so I build with qemu and convert afterwards to the OVF format to be
imported by VirtualBox (for the record Centos Boxes are built similarly
from qemu, then converted)


Reply to: