Build the firecracker microvm filesystem in variant format #2
Description
Is your feature request related to a problem? Please describe.
Currently, the project does not support building the Firecracker microVM filesystem in different (variant) formats. This can limit use cases where specific filesystems are needed for compatibility or specialized workloads.
Describe the solution you'd like
I propose implementing support to automate and build the Firecracker microVM root filesystem in configurable or variant formats (e.g., ext3, ext4, xfs, etc.). This would allow users to select their preferred filesystem type when provisioning microVMs, potentially via a CLI flag or configuration file.
Describe alternatives you've considered
- Manually building the filesystem outside the project and importing it - but this is cumbersome and prone to error.
- Relying on a default filesystem format for all use cases, but this does not address all operational environments.
Additional context
Supporting variant filesystems would increase flexibility and adoption. This feature could integrate with existing VM image build processes and optionally expose filesystem selection in the user interface/configuration.