Install bootc system (centos) from kickstart

[pnagy (Peter Nagy)]

Hi,

I’m having an issue installing bootc based system using a Kickstart file. I’m booting either the latest CentOS Stream 10 minimal iso or a Fedora nightly build, and I’m using the inst.ks parameter to perform the installation from Kickstart. I install it as vm into vmware.

Regardless of the source image I use (CentOS or Fedora), the installation fails with the same error:

Bootc installation does not yet support user-specified mount points.
Unsupported mount points: /boot/efi

This is my Kickstart file:

text
network --bootproto=dhcp --device=link --activate --onboot=on

zerombr
clearpart --all --initlabel
autopart

bootc --source-imgref quay.io/centos-bootc/centos-bootc:c10s

Can you please advise how to resolve this issue, or whether there is a workaround?

I’ve attached a screenshot showing the error message below.

Thank you for your help.

[hricky (Hristo Marinov)]

@pnagy

I’m having an issue installing bootc based system using a Kickstart file. I’m booting either the latest CentOS Stream 10 minimal iso or a Fedora nightly build, and I’m using the inst.ks parameter to perform the installation from Kickstart.

Currently, the Fedora/CentOS bootc project does not officially provide VM images or ISO files, although this should change over the next few Fedora release cycles. For now, the recommended approach is described in the following links:

Provisioning with qemu and libvirt

Bootc-image-builder and image-builder

Hey there. I’ve been asked a few times in different places about bootc-image-builder and image-builder and their differences/backstory. I’ve written the story and future of both down in a blogpost and was asked on Matrix to also share that here. The two things merging is pretty exciting as image-builder is also available in Fedora’s build infrastructure so I hope to work on producing bootc artifacts directly in Koji in the near future as well. Let me know if you have any questions and do try o…

Installers for bootable containers

Hey there. During my Christmas break and since my previous post about the differences between image-builder and bootc-image-builder some people had questions about our progress on building installers out of bootable containers. It made me realize that not many people are familiar with the direction we’re going and that a new installer type, which bases the installer environment on a container, is available. I decided to write a small blogpost about this as well: Installer types for bootable co…

---

@pnagy

I install it as vm into vmware.

The workflows described above work for QEMU/KVM/ISO, but I have not personally tested them on VMware.

[pnagy (Peter Nagy)]

Great! Thank you for info and these resources.

[jikortus (Jiří Kortus)]

Hello @pnagy,

this is a known issue/limitation of bootc, at least we bumped into this problem when testing the bootc kickstart command in Anaconda and have it tracked downstream in https://issues.redhat.com/browse/RHEL-135114. The issue is that bootc doesn’t support specification of arbitrary mount points, and unfortunately those include /boot/efi - which makes the installations with bootc images fail on (U)EFI machines. We hope this will get fixed soon.

[hricky (Hristo Marinov)]

Considering the initial post, it is probably related to the following article:

Introducing the new bootc kickstart command in Anaconda - Fedora Magazine

In my humble opinion, the article is generally good, but it is not comprehensive. It would be great if you could write a more detailed guide including a complete workflow example so I can test it and try to update the following section in the official bootc documentation:

Using Anaconda - Installing Fedora/CentOS bootc on Bare Metal