User Stories:

• As a developer, I want to use bootc for container image installation in Anaconda, so that I'm using consistent tooling with container deployment.
• As a developer, I want to use bootc for container image installation in Anaconda, so that Anaconda code will simplify and some functionality could be used from bootc.
• As a user, I want to use bootc everywhere, so that changes in the bootc are reflected everywhere and I'm working on consistent environment.

Description:

Currently we have a support for ostreecontainer in pykickstart and Anaconda. During the implementation of this, we knew that it will be replaced by bootc which wasn't ready back then. This issue is official request from RHEL image mode by BIFROST-391.

This feature captures the upstream https://github.com/rhinstaller/anaconda/discussions/5197 discussions.

Essentially, we are shifting technological focus from ostree to bootc. bootc has already gained many features that do not live in "ostree container".

Basically: Add a new kickstart verb "bootc" that uses bootc install to-filesystem (the same way bootc image builder does it).

Note that one important technological aspect of this is that "bootc install" expects to be invoked as a container via podman - so we need podman in the ISO environment.

Acceptance criteria:

• There is bootc kickstart command.
• The bootc kickstart command can be used with partial kickstart installation from GUI/TUI.

Third party ACKs:

All the third parties who should be informed of this issue please provide here an ACK in case you agree with this proposed issue. This issue will then be included for the next quarterly planning.