Skip to content
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

docs: Extend rpm-ostree relationship a bit #249

Merged
merged 1 commit into from
Jan 5, 2024

Conversation

cgwalters
Copy link
Collaborator

Based on a question from a chat.

docs/relationship.md Outdated Show resolved Hide resolved
Comment on lines +57 to +59
The way kernel argument work also uses ostree on the backend
in both cases, so using e.g. `rpm-ostree kargs` will also work
on a system updating via bootc.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not fully understanding what is being said here...it seems to conflict with what was previously said about client-side mutation. We want users to define kargs as part of the container image, correct?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Most of the time, yes. But there are also valid use cases for machine-specific kernel arguments, so that continues to work.

@cgwalters cgwalters added the documentation Improvements or additions to documentation label Jan 3, 2024
Based on a question from a chat.

Signed-off-by: Colin Walters <[email protected]>
Copy link
Member

@jmarrero jmarrero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@cgwalters cgwalters merged commit 4a5193e into containers:main Jan 5, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants