#109: vagrant libvirt images only have 3G disk
--------------------+--------------------
Reporter: eparis | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords:
--------------------+--------------------
In a conversation with cwalters he said:
ok here's the deal, qcow2 is a thin-provisioned disk format, fedora uses
40GB by default for vagrant
that's defined here: https://pagure.io/releng/blob/master/f/scripts/build-
cloud-images#_68
now where's that 3GB coming from? here: https://git.fedorahosted.org/cgit
/spin-kickstarts.git/tree/fedora-cloud-base-vagrant.ks
that includes https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree
/fedora-cloud-base.ks#n46
that's outside the VM
now inside, cloud-init normally starts and uses "growpart" early on boot
except in vagrant, it's disabled because hardcoded ssh keys and stuff
so typing: growpart /dev/vda 1
then resize2fs /dev/vda1
i'd say this is really a fedora build system bug - the kickstart should
match the qcow2
it's a one liner fix to spin-kickstarts
-----
So while his commands work I couldn't find a way to get them in early
enough to solve my disk space usage problems. But something is wrong when
vagrant+libvirt images are only 3G and don't auto-grow, for sure.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/109>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
