.Root filesystem are not expanded by default When you use a base container image, that does not include `cloud-init` to create an AMI or QCOW2 container image by using `bootc-image-builder`, the root filesystem size is not expanded dynamically on boot to the full size of the provisioned virtual disk. To workaround this issue, apply one of the following available options: * Include `cloud-init` in the image. * Include custom logic in the container image to expand the root filesystem, for example: ---- /usr/bin/growpart /dev/vda 4 unshare -m bin/sh -c 'mount -o remount,rw /sysroot && xfs_growfs /sysroot' ---- * Include a custom logic to use the additional space for secondary filesystems, for example, `/var/lib/containers`. NOTE: By default, the physical root storage is mounted at the `/sysroot` partition.