What were you trying to do that didn't work?

bootc doesn't support installation with arbitrary mount points (e. g. /var/testmnt), which it explicitly states as an error during installation (using Anaconda's bootc kickstart command in this context):

12:54:23,649 WARNING org.fedoraproject.Anaconda.Modules.Payloads:pyanaconda.modules.common.errors.installation.PayloadInstallationError: Bootc installation does not yet support user-specified mount points. Unsupported mount points: /var/testmnt

Moreover, also EFI installations are affected, as bootc doesn't allow an already existing /boot/efi partition.

What is the impact of this issue to you?

User experience with (bootc) image mode installations may be affected as compared to installations with other payload types (e. g. packages) that offer more partitioning options, including custom mount points for new or existing file systems. Also, it's not possible to install on machines with (U)EFI.

Please provide the package NVR for which the bug is seen:

bootc-1.10.0-2.el10

How reproducible is this bug?:

100%

Steps to reproduce

1. Prepare a kickstart file installing a bootable container image (using bootc command) and custom partitioning with non-standard mount points (e. g. /var/testmnt).
2. Start installation with the kickstart file.

Expected results

Installation with a custom, non-standard mount point is successful, the mount point is accessible in the installed system.

Actual results

Installation fails due to custom mount points not being supported by bootc yet.

Additional notes

This ticket is for downstream tracking. If my understanding is correct, custom mount points are supported now upstream (https://github.com/bootc-dev/bootc/pull/1727).