Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
Add clarity about how when using a kickstart customization, other customization blocks are not supported. This is discussed here: #528
  • Loading branch information
estuart authored and mvo5 committed Dec 10, 2024
1 parent 23e10d7 commit c25cc95
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -399,7 +399,8 @@ The `rootfs` option (or source container config, see [Detailed description of op

### Anaconda ISO (installer) options (`installer`, mapping)

Users can include kickstart file content that will be added to an ISO build to configure the installation process.
Users can include kickstart file content that will be added to an ISO build to configure the installation process. When using custom kickstart scripts the customization needs to be done via the custom kickstart script. For example using a `[customizations.user]` block alongside a `[customizations.installer.kickstart]` block is not supported. See this issue [https://github.com/osbuild/bootc-image-builder/issues/528] for additional detail.

Since multi-line strings are difficult to write and read in json, it's easier to use the toml format when adding kickstart contents:

```toml
Expand Down

0 comments on commit c25cc95

Please sign in to comment.