Building ISO from custom Blue Build images based on Aurora - boots as Fedora Base 41

Hi, I am using Blue Build template to create slightly customized Aurora-DX image (just adding couple of flatpaks, rpm packages and custom justfile). When I build image and rebase to it from standard Aurora-DX (installed via official ISO), it works as expected. I have it as my ghcr.io/mygithubacc/myaurora package with all standard aurora stuff as well as my custom ones. But when I build IOS from this as sudo bluebuild generate-iso --iso-name weird-os.iso recipe recipes/recipe.yml (version 0.9.6) , it works, but when I install it and boot this image, it shows as Fedora Base 41 and rpm-ostree status output is quay.io/fedora-desktops/base:41 instead of expected ghcr.io/mygithubacc/myaurora. So updates are not working etc. But on the other hand aurora customizations are in place, my custom packages from myaurora are also there. Just the "source" address is pointing to wrong image. What I am doing wrong with the build? Thanks a lot!
Solution:
You aren't actually doing anything wrong. Unfortunately, we can't just generate the exact image name to pass to the ISO Builder, so you will need to make sure when you build an ISO from a recipe that you rebase to the proper image.
Jump to solution
8 Replies
Solution
Luke Skywunker
You aren't actually doing anything wrong. Unfortunately, we can't just generate the exact image name to pass to the ISO Builder, so you will need to make sure when you build an ISO from a recipe that you rebase to the proper image.
Luke Skywunker
Now, if you were to use the image version of the ISO builder, it would work.
Meexin
MeexinOP3w ago
So the flow is to generate the iso, install and boot and then rebase back to my ghcr.io package, right?
Luke Skywunker
Only if you build the ISO from the recipe, instead of from the image. Because what's happening in the background is the CLI is building the image locally on your computer and putting it into a tarball and passing that into the ISO builder.
Meexin
MeexinOP3w ago
I see, I will try that, had some issues with this approach where it cannot connect to my private ghcr.io from the VM and on my host OS I still have issues using the cargo version of bluebuild(even latest 0.9.6, still issue with unknown flag --format error). But thanks a lot for clarification!
Luke Skywunker
Did you end up updating the issue that was out there? I don't know what the full context of this error is.
Meexin
MeexinOP3w ago
I wanted at first but then noticed original error was slightly different and I am not sure if there is not some leftover from the previous cargo version or whatever is happening. So was using the included bluebuild in image instead. I can create new issue or folow up on the previous one. I am getting: ╰─ sudo /root/.cargo/bin/bluebuild generate-iso --iso-name weird-os.iso recipe recipes/recipe.yml ─╯ INFO => Recipe recipes/recipe.yml is valid INFO => Templating for recipe at recipes/recipe.yml INFO => Retrieving OS version from ghcr.io/ublue-os/aurora-dx-nvidia-open:latest WARN => Unable to get version via image inspection due to error: × unknown flag: --format
Luke Skywunker
Will you mind creating an issue for this? I'd appreciate as much information as you can. You can use the -vv arg to do Trace Logging.

Did you find this page helpful?