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

install: Stop reading kargs from container root, use ostree #882

Merged
merged 1 commit into from
Nov 8, 2024

Conversation

cgwalters
Copy link
Collaborator

Part of #879

Basically we want to be able to bootc install outside of a container. For the same reasons actually that we already support parsing kargs from an ostree commit (without materializing it as a filesystem), just expose that API via pub(crate) and use it in between the "pull" and "deploy" phases.

We basically do the same thing on bootc upgrade.

@github-actions github-actions bot added the area/install Issues related to `bootc install` label Nov 7, 2024
@cgwalters
Copy link
Collaborator Author

(Existing tests cover this)

@cgwalters

This comment was marked as outdated.

Part of containers#879

Basically we want to be able to `bootc install` outside of
a container. For the same reasons actually that we already support
parsing kargs from an ostree commit (without materializing it
as a filesystem), just expose a small wrapper for that API
via `pub(crate)` and use it in between the "pull" and "deploy" phases.

We basically do the same thing on `bootc upgrade`.

- v2: Clean up the multiple copies of the kargs path into a `const`

Signed-off-by: Colin Walters <[email protected]>
@cgwalters cgwalters merged commit 680b29f into containers:main Nov 8, 2024
31 of 32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/install Issues related to `bootc install`
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants