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

generate-iso: If bootupctl backend generate-update-metadata is not run in the image, ISO install fails #227

Closed
fiftydinar opened this issue Sep 16, 2024 · 1 comment · Fixed by #228
Assignees
Labels
type: fix Iterations on existing features or infrastructure.

Comments

@fiftydinar
Copy link
Contributor

This means that bootc needs to be installed inside the image for the command to be performed.

Jason's Wiki which acknowledges this:
https://github.com/JasonN3/build-container-installer/wiki/known_errors#failed-to-write-boot-loader-configuration

We can either recommend or automate this.

This package is available from F39+, but F39 ships older version, which is not tested.

Will also have to check out if F41 Beta has bootc installed, so we wouldn't need to do the package install for F41+.

@gmpinder gmpinder self-assigned this Sep 16, 2024
@gmpinder gmpinder added the type: fix Iterations on existing features or infrastructure. label Sep 16, 2024
@gmpinder
Copy link
Member

I think a post-install script that is run at the end of the build is the best way to handle this. I can do some local testing to see if the the F39 images will work with that version of bootc. A general check for the existence of the binary can be done and then we can perform an install in the event that it isn't installed. That should cover most bases here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: fix Iterations on existing features or infrastructure.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants