Closed ArneBachmann closed 7 years ago
I must correct myself. When starting with up --no-provision
, the plugin announced to have change the disk size, but after halt
and up --provision
, the file system size was still stuck at the original 10GB, although the VirtualBox GUI shows a disk size of 100GB.
Could it be that the box has some clear text setting that determines the actual visible size? I might have to edit that setting by hand before provisioning.
I found the reason. A box always comes with a pre-partitioned, pre-formatted, and pre-installed OS. Therefore I can do whatever I like (using the disksize plugin, converting disk images by hand), it won´t matter. The only solution seems to use a box that has a formatting that allows dynamic enlarging (e.g. LVM).
Workaround that worked for me: After using the disksize plugin, reconfigure the Vagrant VM to boot from a virtual CD drive or USB media that contains a disk partitioner (e.g. GParted) and resize the disk; afterwards detach virtual CD drive, and Vagrant shouldn run as before. It worked for me, but requires a manual step that does not really feel automagic anymore...
Just as a comment: When using the disksize plugin during initial provisioning, it worked like a charm, the disk was resized prior to OS installation. Box used:
debian/contrib-jessie64
with 100GiB. This saved me so much time!