#120: Fedora 22 Cloud vagrant image does not extend filesystem to disk size
------------------------------+---------------------
Reporter: pwnall | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Future
Component: Cloud Base Image | Resolution:
Keywords: |
------------------------------+---------------------
Comment (by jpeeler):
As long as vagrant-libvirt gets rebased the first part of the problem will
be solved. But I considered this ticket to include automatic resizing of
the image rather than doing manually as you indicated. I personally was
more interested in the atomic image, but both are important. Here's what
I've been doing for the centos atomic image:
config.vm.provision :shell, inline: <<-SHELL
growpart /dev/vda 2
pvresize /dev/vda2
lvresize -l +100%FREE /dev/atomicos/docker-pool
SHELL
I suspect usage of cloud-init is the key to automating, but the centos
atomic image doesn't have cloud-init (fedora does though it seems, hrm).
Finally, there are instructions to add a new disk
(http://www.projectatomic.io/docs/quickstart/), but I prefer to just
resize as that is a lot more automatable.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/120#comment:4>
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
