Fedora CoreOS on Proxmox isn’t officially supported, but it runs fine if you use the QEMU image and feed it an Ignition config. The trick is getting the VM settings right and not fighting the installer.

Grab the QEMU image
FCOS doesn’t ship an ISO. You download the qcow2 image from the download page. Pick the QEMU format, not the bare metal one. The file is compressed with xz, so extract it first.
xz -d fedora-coreos-40.20240701.3.0-qemu.x86_64.qcow2.xz
Now you have a qcow2 file. Proxmox can import that directly.
Create the VM without a disk
Make a new VM in the Proxmox UI. Set the OS type to Linux, and for the machine type pick q35. Give it some RAM and CPU. Do not add a disk yet — we’ll import the qcow2 after.
One thing that trips people up: the SCSI controller. FCOS works with VirtIO SCSI, but if you leave the default LSI controller, the disk won’t be detected. So set the SCSI controller to VirtIO SCSI single.

Import the disk
Upload the qcow2 to your Proxmox storage, then import it with qm importdisk. Replace 100 with your VM ID and local-lvm with your storage.
qm importdisk 100 fedora-coreos-40.20240701.3.0-qemu.x86_64.qcow2 local-lvm
After import, go to the VM’s hardware tab and attach the unused disk as a SCSI device. Make sure it’s on the VirtIO SCSI controller.
Ignition config
FCOS doesn’t have a traditional installer. You give it an Ignition config that tells it what to do on first boot — create users, add SSH keys, write files, start services. You can generate one with the fcct tool.
Here’s a minimal config that adds your SSH key. Save it as config.fcc and compile it.
variant: fcos
version: 1.4.0
passwd:
users:
- name: core
ssh_authorized_keys:
- ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAI... your@email
fcct -p -o config.ign config.fcc
Now you need to get that Ignition file to the VM. The easiest way on Proxmox is to create a second small disk with the config. Make a 1MB raw image, put the Ignition file in it as ignition/config.ign, and attach it as a second disk. FCOS will read it on boot.
mkdir -p /tmp/ignition
echo '{"ignition":{"version":"3.4.0"},"passwd":{"users":[{"name":"core","sshAuthorizedKeys":["ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAI... your@email"]}]}}' > /tmp/ignition/config.ign
mkfs.vfat -n ignition -C /tmp/ignition.img 2048
mcopy -i /tmp/ignition.img /tmp/ignition/config.ign ::/ignition/config.ign
Then attach ignition.img as a second disk. Boot the VM and it’ll provision itself.
The unsupported part
FCOS officially supports bare metal and specific cloud platforms. Proxmox isn’t on the list. It works because Proxmox is just KVM under the hood, but don’t expect the FCOS team to help with Proxmox-specific issues. The GitHub feature request for Proxmox support has been open for years.
That said, I’ve run it in a homelab without trouble. The main gotchas are the SCSI controller and getting the Ignition file to the VM. Once those are sorted, it just works.
If you’re already using cloud-init on Proxmox, the Ignition flow feels similar but with different syntax. See my post on fixing Proxmox cloud-init only creating the default user for a comparison.