Feature Request: Add build-iso workflow ...
🧵 Great job on the presentations guys! I heard that you guys were still not using bootc-image-builder to generate ISOs and then the followup from the guys asking if he could make AMIs made me start thinking. I found the ticket here to use bootc-image-builder but theres not much talk of requirements.
GitHub
Feature Request: Add build-iso workflow · Issue #1 · ublue-os/image...
Purpose Allow a simple workflow to create ISOs from their custom container image. Scope Should only upload to Github Artifacts by default Include instructions on how to upload to external S3 cloud ...
14 Replies
The biggest issue ive dealt with when using this personally in CI is the storage limits
we are using bootc-image-builder on bluefin LTS btw
you might want to check that out
https://github.com/ublue-os/bluefin-lts/blob/main/.github/workflows/buid-iso.yml
ah well then thats super easy. Ill start there
we are just storing the images on aws buckets
that makes WAY more sense. I was gonna ask how youre getting around that 2GiB limit
but i believe that if your image is small/compressed enough you can store it on gh actions artifacts or releases
bib makes really nice ISOs
we had ISOs that were like 3GB
at the start
i think they are still that small
it sure does. been using that for a while. Mine are about 3GB as well
hmm. I can work with this. So were gonna need to provide an optional template where a user can add their own S3 details in to upload their builds. I dont think it makes sense right now to try and compress it so highly that it may/may not hit that 2GiB limit as part of the actions artifacts. Maybe as part of the action artifact it spits out a s3 url of the finished product(s)?
Interesting that for the bluefin pipeline the
bootc-image-builder that yall are using is ghcr.io/centos-workstation/bootc-image-builder:latest as opposed to the image in the docs which says quay.io/centos-bootc/bootc-image-builder:latest
Anyone know if there is a difference? I guess Carl put that there or something to help with speed?nope nothing
its just an older fork
because we had some failures with the recent
bootc-image-builder imagesyeah i ran into those myself. especially around
rootfs. thanks for the contextThe failures were due to
bib images being way out of date. So we forked and built it ourselvesoh wow, thats important context. Any ideas why the images on quay arent being updated?
looking at the registry it did go about 3 weeks without updates and got a new image 2 days ago
They were having some issues with their build pipeline. But simple enough to build it yourself
GitHub
feat(build-iso): Add ability to generate ISO by SNThrailkill · Pull...
This PR adds a new optional workflow to the image template that allows a user to create an ISO using the bootc-image-builder utility. It supports either amd64 and arm64 architectures however not bo...
nooooice ill be checking this out tomorrow