Draft
Conversation
This came out of discussion in CentOS/centos-bootc-dev#27 Basically...I think what we should emphasize in the future is the combination of `bootc` and `dnf`. There's no really strong reason to use `rpm-ostree` at container build time versus `dnf`. Now on the *client* side...well, here's the interesting thing; with transient root enabled, `dnf install` etc generally just works. Of course, *persistent* changes don't. However, anyone who wants that can just `dnf install rpm-ostree` in their container builds. There is one gap that's somewhat important which is kernel arguments. Because we haven't taught `grubby` do deal with ostree, and we don't have bootc-dev/bootc#255 to change kargs per machine outside of install time one will need to just hand-edit the configs in `/boot/loader`. Another fallout from this is that `ostree container` goes away inside the booted host...and today actually this totally breaks bib until osbuild/bootc-image-builder#18 is fixed. Probably bootc should grow the interception for that too optionally.
Collaborator
|
LGTM |
Member
Author
Basically blocked on:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This came out of discussion in CentOS/centos-bootc-dev#27
Basically...I think what we should emphasize in the future is the combination of
bootcanddnf.There's no really strong reason to use
rpm-ostreeat container build time versusdnf. Now on the client side...well, here's the interesting thing; with transient root enabled,dnf installetc generally just works.Of course, persistent changes don't. However, anyone who wants that can just
dnf install rpm-ostreein their container builds.There is one gap that's somewhat important which is kernel arguments. Because we haven't taught
grubbydo deal with ostree, and we don't have bootc-dev/bootc#255 to change kargs per machine outside of install time one will need to just hand-edit the configs in/boot/loader.Another fallout from this is that
ostree containergoes away inside the booted host...and today actually this totally breaks bib until osbuild/bootc-image-builder#18 is fixed.Probably bootc should grow the interception for that too optionally.