Supported Platforms
Fedora CoreOS is provisioned via prebuilt disk images, and configured on first-boot via Ignition. Each platform may require specific logic and components, thus dedicated images are provided for each supported environment. Additionally, a unique platform ID is available in the host environment for runtime introspection.
Supported platforms
The currently supported platforms and their identifiers are listed below.
x86_64
-
Aliyun/Alibaba Cloud (
aliyun): Cloud platform. See Booting on Alibaba Cloud. -
Amazon Web Services (
aws): Cloud platform. See Booting on AWS. -
Microsoft Azure (
azure): Cloud platform. See Booting on Azure. -
Microsoft Azure Stack (
azurestack): Cloud platform. -
DigitalOcean (
digitalocean): Cloud platform. See Booting on DigitalOcean. -
Exoscale (
exoscale): Cloud platform. See Booting on Exoscale. -
Google Cloud Platform (
gcp): Cloud platform. See Booting on GCP. -
IBM Cloud (
ibmcloud): Cloud platform. See Booting on IBM Cloud. -
KubeVirt (
kubevirt): Cloud platform. See Booting on KubeVirt. -
Bare metal (
metal): With BIOS, UEFI or network boot, with standard or 4k Native disks. See Installing on Bare Metal or Live-booting via iPXE. -
Nutanix (
nutanix): Hypervisor. -
OpenStack (
openstack): Cloud platform. See Booting on OpenStack. -
QEMU (
qemu): Hypervisor. See Booting on libvirt -
VirtualBox (
virtualbox): Hypervisor. See Booting on VirtualBox. -
VMware ESXi, Fusion, and Workstation (
vmware): Hypervisor. See Booting on VMware. Fedora CoreOS images currently use hardware version 17, supporting VMware ESXi 7.0 or later, Fusion 12.0 or later, and Workstation 16.0 or later. -
Vultr (
vultr): Cloud platform. See Booting on Vultr.
AArch64
-
Amazon Web Services (
aws): Cloud platform. See Booting on AWS. -
Bare metal (
metal): With UEFI or network boot, with standard or 4k Native disks. See Installing on Bare Metal or Live-booting via iPXE and Booting on the Raspberry Pi 4. -
QEMU (
qemu): Hypervisor. See Booting on libvirt -
OpenStack (cloud platform):
openstack): Cloud platform. See Booting on OpenStack.
s390x
-
IBM Cloud (
ibmcloud): Cloud platform. See Booting on IBM Cloud. -
Bare metal (
metal): From disk or network boot. See Installing on Bare Metal or Live-booting via iPXE. -
QEMU (
qemu): Hypervisor. See Booting on libvirt -
OpenStack (cloud platform):
openstack): Cloud platform. See Booting on OpenStack.
Runtime introspection of platform IDs
Each Fedora CoreOS image boots with a platform-specific identifier, available on the kernel command-line. The name of the parameter is ignition.platform.id. The platform ID is consumed by OS components such as Ignition and Afterburn. Additionally, it can be used in systemd units via ConditionKernelCommandLine=.
See Ignition’s Supported Platforms and Afterburn’s Supported Platforms documentation pages for more details about which features are supported for each platform. Note that some platforms are currently supported by Ignition and Afterburn but are not yet supported by Fedora CoreOS.
The Platform ID can be introspected at runtime, as follows:
$ grep -o ignition.platform.id='[[:alnum:]]*' /proc/cmdline
ignition.platform.id=awsWant to help? Learn how to contribute to Fedora Docs ›