Skip to content

Commit 24ffc3a

Browse files
estuartmvo5
authored andcommitted
Update README.md
Add clarity about how when using a kickstart customization, other customization blocks are not supported. This is discussed here: #528
1 parent e3be218 commit 24ffc3a

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -443,7 +443,8 @@ The `rootfs` option (or source container config, see [Detailed description of op
443443

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

446-
Users can include kickstart file content that will be added to an ISO build to configure the installation process.
446+
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.
447+
447448
Since multi-line strings are difficult to write and read in json, it's easier to use the toml format when adding kickstart contents:
448449

449450
```toml

0 commit comments

Comments
 (0)