Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1061062

Bug#989462: set Vagrant box filesystem size to something much larger than 20GB

Show all headers | View raw

Package: cloud.debian.org

The Vagrant guidelines say:

"you should create a dynamically resizing drive with a large maximum size. This 
causes the actual footprint of the drive to be small initially, but to 
dynamically grow towards the max size as disk space is needed, providing the 
most flexibility for the end user."
https://www.vagrantup.com/docs/boxes/base

Both VirtualBox and libvirt qcow2 formats support exactly that.  The official 
Debian box seems to be set at a fixed 20GB.  This makes it very difficult for 
F-Droid to use these images as the base box for our Vagrant boxes.
https://gitlab.com/fdroid/fdroid-bootstrap-buildserver/-/issues/10

F-Droid's base box has been using 1TB for a long time with good results.
gitlab.com/fdroid/basebox/

Once this is fixed in Debian's images, then F-Droid no longer needs the forked 
base box and can use only Debian's.

Back to linux.debian.bugs.dist | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Bug#989462: set Vagrant box filesystem size to something much larger than 20GB Hans-Christoph Steiner <hans@eds.org> - 2021-06-04 12:40 +0200
  Bug#989462: set Vagrant box filesystem size to something much larger than 20GB Emmanuel Kasper <emmanuel@libera.cc> - 2021-06-04 15:40 +0200
    Bug#989462: set Vagrant box filesystem size to something much larger than 20GB Hans-Christoph Steiner <hans@eds.org> - 2021-06-04 17:40 +0200
  Bug#989462: set Vagrant box filesystem size to something much larger than 20GB Emmanuel Kasper <manu@debian.org> - 2021-06-07 10:20 +0200

csiph-web