I rebuilt and uploaded the 12 boxes concerned by this bug, should be OK now.
For virtualbox vagrant boxes, please find new box releases at
https://app.vagrantup.com/debian
Libvirt boxes are pending.
Extending the disk image to 20GB slows the build process a bit, as we need to
zero free a bigger filesystem, but it is still acceptable.
--
Diese Nachricht wurde von mein
Hi,
I wonder if it's really so useful to be prepared like this for a change
of hypervisor.
Of course, it's a nice feature, but you trade in at least this
disadvantage of not being able to resize the virtual disk out-of-the-box
(ie, without converting it again, which makes it a bit pointless
> Vagrant base boxes apparently use a maximum disk size of 10G.
OTOH the chosen format of the virtual disks does not allow to increase
the size (VBoxManage refuses to do so).
yes true. The reason is that during the build process, we convert the
raw disk image produced by packer to vmdk. Vmdk is ki
Package: cloud.debian.org
Severity: normal
Dear Maintainer,
Vagrant base boxes apparently use a maximum disk size of 10G.
OTOH the chosen format of the virtual disks does not allow to increase the size
(VBoxManage refuses to do so).
It's probably not helpful to point out in detail why *WE* woul
5 matches
Mail list logo
