You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, when the operator specifies their own kickstart (e.g. adds custom steps or an empty string to force an interactive installer), this step is not added through osbuild. Therefore, the operator must be aware of this command (which is not documented anywhere!) and explicitly add it to the config file.
This function which adds that bootc switch command seems to be exiting early when the operator provides any sort of content in the kickstart (including a blank string - ""), so the command wouldn't be present in the resulting ISO unless this is explicitly defined in the config.toml input.
The text was updated successfully, but these errors were encountered:
I feel that since we have ostreecontainer in our kickstart unconditionally (even when a user provided kickstart is there), that we should probably do the same with bootc switch?
Alternatively we can document that users need to add this always but that seems a bit less friendly.
Before I make the change in images, is it intended to be permanent or is the plan that kickstarts' ostreecontainer be changed to take care of this eventually?
When creating a BIB image without specifying a kickstart script in the configuration, the following command is added as a %post step:
(source)
However, when the operator specifies their own kickstart (e.g. adds custom steps or an empty string to force an interactive installer), this step is not added through osbuild. Therefore, the operator must be aware of this command (which is not documented anywhere!) and explicitly add it to the config file.
This function which adds that
bootc switch
command seems to be exiting early when the operator provides any sort of content in the kickstart (including a blank string - ""), so the command wouldn't be present in the resulting ISO unless this is explicitly defined in the config.toml input.The text was updated successfully, but these errors were encountered: