README: De-emphasize specifying user configuration #135
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per the changes here, it is very much expected that users create their own derived containers as the starting point to the system, not just running the base image.
And once one does that, per the docs there are multiple solutions for injecting and managing authentication credentials, lifecycled with the container image as is often desired.
There's obviously use cases for injecting user configuration, this change just de-emphasizes it and links to the existing centos-bootc docs.