-
Notifications
You must be signed in to change notification settings - Fork 79
support bootc verb in bootc-installer #2040
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
anaconda has recently got a new verb for bootc container images. This commit adds support for it. It's currently opt-in via yaml definitions before we decide how to enable it automatically for relevant distros.
|
Marked as ready for review since the related osbuild PR has been merged. |
bcl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, after fixing the conflict.
|
|
||
| // BootcInstallVerb controls which directive to use in kickstart files for bootc installer ISOs. | ||
| // Valid values are "ostreecontainer" (default) and "bootc" | ||
| BootcInstallVerb *string `yaml:"bootc_install_verb,omitempty"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does not have to be a pointer, empty string is a good default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is fine to have but needs rebasing and linter appeasement.
A small question, if Anaconda supports the bootc verb depends on the Anaconda version but we do not have bootc definitions per-version (as we don't really know what we're building).
Should this then be left to the user or container build to determine instead of the YAML definitions which would apply to all? I can imagine it not specifically making sense for us to inject a kickstart in bootc-installer but that having to be done in the installer container instead?
| image_func: "bootc_legacy_iso" | ||
| # Uncomment the following lines to use the bootc verb instead of ostreecontainer | ||
| # installer_config: | ||
| # bootc_install_verb: bootc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is under anaconda-iso, should it be under bootc-installer instead?
|
This PR is stale because it had no activity for the past 30 days. Remove the "Stale" label or add a comment, otherwise this PR will be closed in 7 days. |
|
Not stale. |
Anaconda has recently got a new verb for bootc container images, this commit adds support for it for bootc-installer.
This is currently opt-in via yaml configs, we need to decide how to enable it automatically.
The code is testable with this
Containerfile:and this command:
Note that you have to have osbuild with osbuild/osbuild#2242, marking as a draft until it gets merged.