bootc generic-iso using ostree rootfs by brlane-rht · Pull Request #2414 · osbuild/image-builder

brlane-rht · 2026-06-11T23:25:59Z

This changes the bootc generic-iso so that the rootfs is the same as the bootc PXE image type.

Note that this currently doesn't actually work right. Something is wrong with how dracut or ostree is setting up the booted filesystem, it doesn't mount things correctly so on boot a number of services fail:
FIXED -- ends up dmsquash-live treats LiveOS/rootfs.img differently, switched to using LiveOS/squashfs.img and now it boots the same as bootc PXE tar.

This also renames it to generic-iso, and it drops the support for embedding a container payload since this isn't an installer iso and is not a raw filesystem (I think the user can do the same thing when setting up their bootc container, but have not explored that).

supakeen · 2026-06-13T15:39:06Z

Will need some careful review; at least the name change will immediately break things for users and the non-embedding of containers (while I agree this can probably be done inside the bootable container itself and it's likely better there) is the same.

FIXED -- ends up dmsquash-live treats LiveOS/rootfs.img differently, switched to using LiveOS/squashfs.img and now it boots the same as bootc PXE tar.

In what way? I'm interested what the behavioral difference is.

I'm also tagging in @ondrejbudai since he's done a bunch with the ISOs for bootc too 🙂.

brlane-rht · 2026-06-15T22:05:46Z

Will need some careful review; at least the name change will immediately break things for users and the non-embedding of containers

Not sure what to do about that.

FIXED -- ends up dmsquash-live treats LiveOS/rootfs.img differently, switched to using LiveOS/squashfs.img and now it boots the same as bootc PXE tar.

In what way? I'm interested what the behavioral difference is.

When it is named squashfs.img it uses overlayfs and when it is rootfs.img it uses device-mapper:

https://github.com/dracut-ng/dracut/blob/main/modules.d/70dmsquash-live/dmsquash-live-root.sh#L330

is the section. With device-mapper the ostree root setup doesn't properly mount things and then a whole mess of services don't start (it actually still boots, which is surprising).

brlane-rht · 2026-06-25T21:27:58Z

I've fixed some issues I was having with fstab mounts (have to pass fstab=no to the kernel/systemd), and added a README that is read from the file storage and written to the ISO, similar to the one in the PXE tar.

I've also experimented with running podman pull ... in the Containerfile and my simple tests work inside the booted system so you can still embed other containers.

schutzbot · 2026-06-25T21:29:40Z

This PR changes the image-builder API or behaviour causing integration failures with osbuild-composer. The next update of the image-builder dependency in osbuild-composer will need work to adapt to these changes.

This is simply a notice. It will not block this PR from being merged.

brlane-rht · 2026-06-25T21:30:41Z

Not sure what's up with the manifest check. Running ./tools/gen-manifest-checksums.sh works fine locally (and I've updated the checksums).

lzap · 2026-06-26T09:59:41Z

Not sure what's up with the manifest check. Running ./tools/gen-manifest-checksums.sh works fine locally (and I've updated the checksums).

There are some compilation errors, thus manifests are not generated correctly?!

Error: pkg/image/container_based_iso.go:106:56: cannot use osTreePipeline (variable of type *"github.com/osbuild/image-builder/pkg/manifest".OSFromContainer) as "github.com/osbuild/image-builder/pkg/manifest".TreePipeline value in argument to manifest.NewISOTree: *"github.com/osbuild/image-builder/pkg/manifest".OSFromContainer does not implement "github.com/osbuild/image-builder/pkg/manifest".TreePipeline (missing method Platform)
Error: pkg/image/container_based_iso.go:106:72: cannot use bootTreePipeline (variable of type *"github.com/osbuild/image-builder/pkg/manifest".EFIBootTree) as []"github.com/osbuild/image-builder/pkg/manifest".ISOBootloader value in argument to manifest.NewISOTree
Error: pkg/image/container_based_iso.go:111:18: isoTreePipeline.RootfsCompression undefined (type *"github.com/osbuild/image-builder/pkg/manifest".ISOTree has no field or method RootfsCompression)
Error: pkg/image/container_based_iso.go:115:18: isoTreePipeline.KernelOpts undefined (type *"github.com/osbuild/image-builder/pkg/manifest".ISOTree has no field or method KernelOpts

I think I know what is happening: unit and build tests do pass because they only test the tip of the branch. However, manifest generation is performed on every single commit individually. One of your commits does not compile correctly.

brlane-rht · 2026-06-26T15:27:24Z

~~Ah, right, I'd forgotten it tried on every commit. Problem is I don't want to make every commit compile, they're easier to read as distinct changes that then converge.~~
Ends up compile failures are skipped, this was failing because the checksums needed to be updated :)

@ostree

Remove the rootfs compression code, it is now created by BootcRootFS and is included in the treePipeline. Use the ISOBootloader list and common bootloader code from iso_bootloaders. This allows the iso to support other arches and bootloader configurations. Also adds optional support for setting the ostree= value in the grub.cfg file when SetOSTREE is true. KernelOpts must already contain 'ostree=@ostree@' if this option is used. It will add the org.osbuild.ostree.grub stage which mounts the rootfs.img, examines the ostree filesystem to extract the boot path and then substitute it for @ostree@ in the grub.cfg file. Related: HMS-10627

dmsquash-live-root treats squashfs.img and rootfs.img differently, it uses the same codepath as http root for squashfs.img which is where the root filesystem detection (looking for /usr or /ostree) is triggered. If rootfs.img is used dracut sets up the root using device-mapper instead of overlay, and this does not work with ostree. Related: HMS-10627

The partition is needed for installing bootc to a partitioned disk image, and the erofs settings are used for the rootfs of the iso. Related: HMS-10627

This changes to using the bootc container directly instead of the deployed filesystem. It builds on top of BootcRootFS (also used by the bootc PXE tar image type). It uses the iso and installer customizations from the bootc distro YAML for setting up the rootfs compression and optional kernel arguments. It also uses the common bootloaders functions which should make it easier to eventually add support for other platforms. Related: HMS-10627

This starts by making sure the required modules have been included in the container's initrd. It also hooks up the blueprint customizations, and uses the YAML for the iso configuration (erofs or squashfs rootfs type). Related: HMS-10627

It's redundant and makes the ibcli image names longer than they need to be. Related: HMS-10627

This adds generation of the manifest checksums. Related: HMS-10627

Set the menu timeout if it is non-zero. 0 means use the stage default, so it is always safe to set it. Related: HMS-10627

Related: HMS-10627

Also adds tests. Related: HMS-10627

Related: HMS-10627

This adds a README to the root of the ISO that describes how to build it using image-builder. This also adds a somewhat generic method for adding files from the data store to the ISO. Resolves: HMS-10627

brlane-rht requested a review from supakeen June 11, 2026 23:27

brlane-rht force-pushed the HMS-10627-bootc-iso branch 2 times, most recently from 4f1b580 to 5a6c3bd Compare June 12, 2026 19:12

supakeen requested a review from ondrejbudai June 13, 2026 15:39

brlane-rht force-pushed the HMS-10627-bootc-iso branch from d2983aa to 56545de Compare June 16, 2026 23:30

brlane-rht force-pushed the HMS-10627-bootc-iso branch from 56545de to cb45918 Compare June 25, 2026 21:18

brlane-rht marked this pull request as ready for review June 25, 2026 21:25

brlane-rht requested review from a team, achilleas-k and thozza as code owners June 25, 2026 21:25

brlane-rht added 12 commits June 26, 2026 08:39

bootc-generic-iso: Add partition information and erofs settings

7be2027

The partition is needed for installing bootc to a partitioned disk image, and the erofs settings are used for the rootfs of the iso. Related: HMS-10627

bootc_imagetype: Use new container_based_iso

1515a9c

This starts by making sure the required modules have been included in the container's initrd. It also hooks up the blueprint customizations, and uses the YAML for the iso configuration (erofs or squashfs rootfs type). Related: HMS-10627

bootc-generic-iso: Drop the bootc- part of the name

b152582

It's redundant and makes the ibcli image names longer than they need to be. Related: HMS-10627

manifest-checksums: Add the bootc pxe-tar-xz image

0207af0

This adds generation of the manifest checksums. Related: HMS-10627

iso_bootloaders: Add support for menu timeout

9ddbfbf

Set the menu timeout if it is non-zero. 0 means use the stage default, so it is always safe to set it. Related: HMS-10627

manifest: Add MenuTimeout to InstallerCustomizations

3ec1b9f

Related: HMS-10627

iso_bootloaders: Set MenuTimeout from InstallerCustomizations

efbaf62

Also adds tests. Related: HMS-10627

bootc_imagetype: Use menu timeout from iso.yaml

ca8cf25

Related: HMS-10627

bootc: Adding a README to generic-iso

1301d1e

This adds a README to the root of the ISO that describes how to build it using image-builder. This also adds a somewhat generic method for adding files from the data store to the ISO. Resolves: HMS-10627

brlane-rht force-pushed the HMS-10627-bootc-iso branch from cb45918 to 1301d1e Compare June 26, 2026 15:44

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

bootc generic-iso using ostree rootfs#2414

bootc generic-iso using ostree rootfs#2414
brlane-rht wants to merge 12 commits into
osbuild:mainfrom
brlane-rht:HMS-10627-bootc-iso

brlane-rht commented Jun 11, 2026 •

edited

Loading

Uh oh!

supakeen commented Jun 13, 2026 •

edited

Loading

Uh oh!

brlane-rht commented Jun 15, 2026

Uh oh!

brlane-rht commented Jun 25, 2026

Uh oh!

schutzbot commented Jun 25, 2026

Uh oh!

brlane-rht commented Jun 25, 2026

Uh oh!

lzap commented Jun 26, 2026 •

edited

Loading

Uh oh!

brlane-rht commented Jun 26, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

brlane-rht commented Jun 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

supakeen commented Jun 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

brlane-rht commented Jun 15, 2026

Uh oh!

brlane-rht commented Jun 25, 2026

Uh oh!

schutzbot commented Jun 25, 2026

Uh oh!

brlane-rht commented Jun 25, 2026

Uh oh!

lzap commented Jun 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

brlane-rht commented Jun 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

brlane-rht commented Jun 11, 2026 •

edited

Loading

supakeen commented Jun 13, 2026 •

edited

Loading

lzap commented Jun 26, 2026 •

edited

Loading

brlane-rht commented Jun 26, 2026 •

edited

Loading