Installing on generic infrastructure
Not every deployment platform is explicitly covered by this project. However, the aim of this project is to support deployment anywhere that runs Linux as a general rule.
Using Anaconda for generic installations
Many virtualized environments can be configured to boot via an ISO (or PXE); then the Installing on bare metal path can be used to install.
Using bootc-image-builder and raw files
The bootc-image-builder tool can generate e.g. raw
disk images from the container image, which can often be transformed
via additional tooling into a format suitable for a specific
virtualization platform.
For more, see qemu and libvirt.
Using bootc install to-existing-root
The bootc install to-existing-root
path supports installing "inside" an existing running Linux system, effectively
replacing its contents with the container image. This allows provisioning
systems using existing disk images already uploaded and managed
as part of the virtualization platform.
As a convenience, system-reinstall-bootc can be used in place of bootc install to-existing-root.
See the system-reinstall-bootc docs
for details.
Requirement to provide filesystem type
Fedora base images from this project do not specify a default root filesystem.
CentOS Stream defaults to xfs.
Some provisioning tools (such as Anaconda) provide their own defaults,
while others (bootc-image-builder, bootc install to-disk) require
explicit configuration.
You can configure the default root filesystem at build time
via bootc install-config,
or at deployment time via bootc-image-builder’s --rootfs.
Want to help? Learn how to contribute to Fedora Docs ›