[Bug 1580596] [NEW] Xenial & bionic vagrant box disk size is too small

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Pat Viafore (patviafore):

[Impact]
Users could not use vagrant boxes as a full computer (or anything requiring more than 10G of memory). This was a regression from our behavior in 14.04

[Test Case]

vagrant init ubuntu/bionic64 (replace with ubuntu/eoan64 or ubuntu/xenial64 as needed)
vagrant up
vagrant ssh default
Run `df -H` inside the vagrant box
Observe Disk size of drive mounted at / (before the fix it will list ~10G, after the fix it will list ~40G)

[Regression Potential]

Making the disk size bigger for vagrant boxes does not increase the size
of the box when running (not until that extra size is used). Therefore,
the regression potential is low, as users with under 40G of disk space
are still able to launch the new Vagrant images without running out of
space.

The 40G was also present in 14.04, which should improve confidence that
our users can use 40G Vagrant images. This has also released with 20.04.

[Original Description]
The ubuntu/xenial64 box has only 10GB of disk whereas it was 40GB with the trusty box.

This makes the box not really usable as a desktop computer.

** Affects: cloud-images
     Importance: High
     Assignee: Pat Viafore (patviafore)
         Status: Fix Committed

** Affects: google-app-engine-django
     Importance: Undecided
     Assignee: Pat Viafore (patviafore)
         Status: New

** Affects: livecd-rootfs (Ubuntu)
     Importance: Undecided
     Assignee: Pat Viafore (patviafore)
         Status: Fix Released

-- 
Xenial & bionic vagrant box disk size is too small
https://bugs.launchpad.net/bugs/1580596
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.