feat(iso): Create generate-iso command

blue-build / cli

BlueBuild's command line program that builds custom Fedora Atomic images based on your recipe.yml

https://blue-build.org/

Apache License 2.0

71 stars 8 forks source link

feat(iso): Create generate-iso command #192

Closed gmpinder closed 4 weeks ago

gmpinder commented 3 months ago

Tasks

[x] Add ctrl-c handler to kill spawned children
[x] add more args to support all variables
[x] Add integration test

fiftydinar commented 3 months ago

Can't see from the commits, does this uses this action?

https://github.com/JasonN3/build-container-installer

Bundling flatpaks inside the ISO from the default-flatpaks module recipe would be also great.

However, I find that it doesn't work properly in my testing for some reason (flatpaks installed, but they miss refs, hence they failed to update). However, I use custom named flathub-system remote instead of flathub so maybe that's what contributed to it.

gmpinder commented 3 months ago

Can't see from the commits, does this uses this action?

https://github.com/JasonN3/build-container-installer

Bundling flatpaks inside the ISO from the default-flatpaks module recipe would be also great.

However, I find that it doesn't work properly in my testing for some reason (flatpaks installed, but they miss refs, hence they failed to update). However, I use custom named flathub-system remote instead of flathub so maybe that's what contributed to it.

I'm still working on the implementation, but yes I'll be using the image from that action to build the ISO. I've got a lot of testing to do and I'd appreciate y'all testing it out too when I get it into a decent state

fiftydinar commented 2 months ago

It seems that latest Fedora 40 images require bootupd to be installed & bootupctl backend generate-update-metadata command to be done inside the image. Fedora 39 images don't support this operation (but also don't have this issue). The command updates the bootloader metadata which would be further used by bootc in installer to update the bootloader data inside the system to latest version. That's how I understand it.

Maybe old Anaconda versions prior to latest 1.2.1 install the older bootloader version, which is not compatible with the kernel. 1.2.1 adds the support for using bootc to circumvent this issue. This is just a speculation, I'm not sure.

I made the issue in upstream ISO generator repo: https://github.com/JasonN3/build-container-installer/issues/127