https://blue-build.org/ logo
Failed to create ISO from recipe
# questions
a
message has been deleted
c
I don't think I can send the entire error as text to my phone without KDE Connect, but I can manually type out what I think is the important line. I'm trying to create a lightly customized version of Fedora Budgie Atomic for myself, and I get an error saying something like this when trying to build it as a test. I was able to find an answer to a previous problem I had by searching in this server, but not this time. Is there any obvious cause and easy solution for this? It also complains about Error 1 on line 2 and Error 2 on line 148 of the makefile, which is hopefully enough to get pointed in the right direction when combined with the error message.
Copy code
time="2026-05-12T22:08:13Z" level=fatal msg="initializing source oci-archive:/img_src/charlie.tar.gz:: creating temp directory: archive file not found: \"/img_src/charlie.tar.gz\""
I may have forgotten to tag this. Oops.
I think my only option is to just build the ISO from a published image, but the problem with that is that I have no clue how to publish one and can't find anything in the docs. I'm probably just being blind.
x
is your repo generated from the template? image publishing is built in if you are on github
otherwise, look at
bluebuild build --help
, you'll want
--push
at least
as for the ISO generation error, i genuinely don't know what the issue is, it could be something regarding how CLI wraps build-container-installer/ or it could be an issue in that project itself
c
Does using the workshop to create the repo count as using the template? Because that's how I did it.
x
yes it does
if you used that, you should already be publishing images on github automatically
m
Hmm I'm running into this as well. I do have image publishing working so I'll try building it from that image. Did that work for you?
c
Honestly, I kinda just gave up and forgot. Maybe something's fixed itself in the time since then, but I'd have to set up the building stuff again to check.
g
I've got a [PR](https://github.com/blue-build/cli/pull/728) for trying to fix this, but I haven't gotten back around to it
I also have plans to completely replace the current ISO generator, so this might not even be an issue when I'm done (whenever that may be...)
m
Hmmm, well I got the building from an image to work but there isnt anything actually in the output directory 🤔 I ran the following:
Copy code
bluebuild generate-iso -vv --iso-name ${{forgejo.ref_name}}-tillos.iso --tempdir temp -o iso image forge.bcstuff.io/bcfranchise-public/tillos-cosmic-nvidia:br-${{forgejo.ref_name}}-44

tree
and it says its building, but there isnt anything in the
iso
directory. I also saw a
build
dir referenced in the logs but theres no directory called
build
either... Heres how it parsed my generate-iso command too:
Copy code
command: GenerateIso(
        GenerateIsoCommand {
            command: Image {
                image: "forge.bcstuff.io/***-public/tillos-cosmic-nvidia:br-0.0.4-44",
            },
            output_dir: Some(
                "iso",
            ),
            variant: Kinoite,
            secure_boot_url: "https://github.com/ublue-os/bazzite/raw/main/secure_boot.der",
            enrollment_password: "universalblue",
            iso_name: Some(
                "0.0.4-tillos.iso",
            ),
            web_ui: false,
            tempdir: None,
            platform: None,
            drivers: DriverArgs {
                build_driver: None,
                inspect_driver: None,
                signing_driver: None,
                run_driver: None,
                boot_driver: None,
            },
        },
    )
I did notice in the tests in your PR you test the command but dont assert that the ISO is actually present in
ISO_OUT
so i wonder if its failing there too
g
Yeah I started, but didn't end up getting anywhere. This year has been a bit of a wash for me when it comes to working on the project. Though I think I'm starting to get back into the swing of things
There's some actual logic that's wrong in the code somewhere. The tests were created to help me find the problem
m
Hey so I tried to just directly go use the https://github.com/JasonN3/build-container-installer action and it did the same thing where it appears to be creating an ISO properly but it just doesnt copy it out of the container its using. I also replicated that with bluebuild and I can see it make the iso in the build container it makes, but then it finishes without putting it anywhere outside of the container 😅 Idk if thats helpful, but it definitely seems like its a
build-container-installer
issue
x
could you perhaps use a subsequent gh action to upload the iso somewhere?
m
Unfortunately I cant get it out of the build-container-installer container for some reason. I finally did get it to work just locally in docker compose with something like this:
Copy code
build-container-installer:
    image: ghcr.io/jasonn3/build-container-installer:main
    privileged: true
    volumes:
      - ./direct/workspace:/github/workspace/
      - ./direct/dnf-cache:/cache/dnf
      - ./direct/dnf_new:/cache/dnf_new
    command: |
      ARCH=x86_64 \
      DNF_CACHE="/cache/dnf" \
      ENROLLMENT_PASSWORD=container-installer \
      IMAGE_NAME=<REDACTED> \
      IMAGE_REPO=<MY_REPO> \
      IMAGE_TAG=br-0.0.6-44 \
      ISO_NAME="/github/workspace/0.0.6-<REDACTED>.iso"
Strangely the ISO is generates does work, but behaves slightly differently that when I install the OS by first using Fedora Atomic Cosmic then using
bootc switch
to install it. But at least it works lol
2 Views