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

chore: add bootc to all images #581

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

chore: add bootc to all images #581

wants to merge 1 commit into from

Conversation

m2Giles
Copy link
Member

@m2Giles m2Giles commented May 16, 2024

39 cannot use the bootupctl command with the updated installer.

40 needs the bootupctl command and the updated installer.

40 currently has an issue with rpmfusion. I would like to confirm that a downstream image doesn't have to convert again.

Thank you for contributing to the Universal Blue project!

Please read the Contributor's Guide before submitting a pull request.

@m2Giles
Copy link
Member Author

m2Giles commented Jun 20, 2024

While bootc will be the future, I'm wondering if we should hold off on having these on all images while the supporting infrastructure is still being put in place.

The command to make the iso work on F40 causes it to break on F39. This can be handled via an if statement during build. But maybe a point of concern for downstream images where if it isn't rerun the iso will break.

@@ -6,6 +6,7 @@
"android-udev-rules",
"apr",
"apr-util",
"bootc",
Copy link
Contributor

Choose a reason for hiding this comment

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

My nitpick, lets make the spacing on this line consistent with others. :-)

@bsherman
Copy link
Contributor

While bootc will be the future, I'm wondering if we should hold off on having these on all images while the supporting infrastructure is still being put in place.

The command to make the iso work on F40 causes it to break on F39. This can be handled via an if statement during build. But maybe a point of concern for downstream images where if it isn't rerun the iso will break.

I support adding bootc ... and I think we had this in the past, no?

Users of bootc would be experimental/early-adopters who are fine with it's explicit lack of support for local layering.
Thus, all our docs which talk about command-line stuff should continue to reference rpm-ostree operations.

I don't know how ISO building has anything to do with having the binary on an image to support the bootc effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants