Hey all, I struggled with the title a bit, but I’m trying to figure out how to take a container image and use it with coreos-installer to simplify the deployment process (eliminating rebases).
I did see that there was a recent repo (custom-coreos-disk-images), which I believe is intended to do the job, but I wasn’t able to get it to function when I attempted to containerize it (osbuild-mpp outputs a stack trace when attempting to find an *.img file).
Is there another method for generating compatible image for bare metal x86_64 deployment or will the ociarchive work with coreos-installer?
I’m not quite sure I fully understand what you mean and are trying to achieve. Could you please try to explain it in more detail and precisely?
The repo you mentioned is for Red Hat Enterprise Linux CoreOS (RHCOS), which is downstream of Fedora CoreOS (FCOS), it is a single-purpose container operating system and is the default OS for all OpenShift Container Platform cluster machines.
From Fedora Linux 42 onwards, Fedora CoreOS will move updates from OSTree to OCI. This change is only scoped to switching to OCI as the transport for Fedora CoreOS content. As before, derivation of Fedora CoreOS images is possible, but it is not yet fully supported nor documented.
Until progress is made on these topics, it is recommended to stick to official images, using Ignition and rpm-ostree to make your changes.
containerizing that software is going to be hard. OSBuild really requires to be run in a VM for now.
Instead of trying to containerize it first, why don’t you try following the README to see if it works for you and only then try to take the next step.
I’ll also note that Live ISO support was recently added to custom-coreos-disk-images so you could generate ISO or PXE media (via --platforms live) from your container and use that for the install (i.e. prevents you having to keep track of a separate metal.raw image).
This is interesting and I will try it. I didn’t read the script and since the README explicitly says RHCOS, I didn’t realize that FCOS was supported. It might be worth considering at least a brief mention of FCOS in the README.