From 457170a92c7b905aa8ace80583a47180b6d2bd38 Mon Sep 17 00:00:00 2001 From: Pat Viafore Date: Fri, 10 Apr 2020 15:18:14 -0500 Subject: [PATCH] Make Ubuntu Vagrant box 40G. (LP: #1580596) Vagrant images were previously put at 10G, but this was a regression from Trusty, in which they were 40G. This made it a tough sell for users to upgrade if they were using a Ubuntu desktop experience. This change does not impact disk usage as Vagrant with the virtualbox provider dynamically allocates space with the VMDK. On a test system, the VMDK took up 1.1G of disk space according to df, and after creating a 2G file in Vagrant, the VMDK grew to 3.1G. Therefore, users who are running on a system with little free space will not see adverse effects if they upgrade to a new vagrant image --- debian/changelog | 6 ++++++ live-build/ubuntu-cpc/hooks.d/base/vagrant.binary | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index 474e24b4..a6786dc9 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +livecd-rootfs (2.525.44) bionic; urgency=medium + + * Increase Vagrant disk size from 10G to 40G (LP: #1580596) + + -- Patrick Viafore Fri, 22 May 2020 15:16:16 -0500 + livecd-rootfs (2.525.43) bionic; urgency=medium [ David Krauser ] diff --git a/live-build/ubuntu-cpc/hooks.d/base/vagrant.binary b/live-build/ubuntu-cpc/hooks.d/base/vagrant.binary index 5e95c334..7610ba63 100755 --- a/live-build/ubuntu-cpc/hooks.d/base/vagrant.binary +++ b/live-build/ubuntu-cpc/hooks.d/base/vagrant.binary @@ -97,7 +97,7 @@ distro=$(chroot chroot lsb_release --id --short | tr [:upper:] [:lower:]) # Get the VMDK in place prefix="${distro}-${suite}-${version}-cloudimg" vmdk_f="${box_d}/${prefix}.vmdk" -create_vmdk ${derivative_img} ${vmdk_f} +create_vmdk ${derivative_img} ${vmdk_f} 40960 #################################### # Create the ConfigDrive