build-iso workflow fails to find manifest

[kervin5]

Looking for some guidance regarding this error message. I'm using the template without any changes other than entering the name of my repo in bluefin-test/iso.toml.

Copying blob sha256:9dad063a624b62064bf25dbbc2e802e472d636056f661f2a0be73efd8a4da98b
Copying blob sha256:15fc5c141ede52009245812dbeb9bbfc7e3c8430e79172af26dfbbe2924e5fe6
Copying config sha256:cacf99c40b177676f122eff793fb854165237df9052ab85bee1fa85687ece47e
Writing manifest to image destination
cacf99c40b177676f122eff793fb854165237df9052ab85bee1fa85687ece47e
Run DESIRED_UID=$(id -u)
Trying to pull ghcr.io/centos-workstation/bootc-image-builder:latest...
Getting image source signatures
Copying blob sha256:dbd3a00db5a7eda689726724cda9f492b4b69c7c2debf35ba56df7425d4881d2
Copying blob sha256:e3c3beac4d5fa7cf2403dc6bc99c329c63a3d4182dc4dcba69165df259548775
Copying config sha256:3893498e5a7a8838c5b2f44fe6cd270bd077e0b6d48249d81b3ff575ee46f969
Writing manifest to image destination
Generating manifest manifest-iso.json
WARNING: --local is now the default behavior, you can remove it from the command line
Manifest generation step
2025/04/24 05:29:14 error: cannot build manifest: cannot get manifest: could not find def file for distro bazzite-42

[hanthor]

osbuild/bootc-image-builder#904

Bazzite edits the is release file so the ISO builder doesn't know it's fedora.

[Gankarloo]

same for me but instead of bazzite it's bluefin-42
2025/05/23 14:25:47 error: cannot build manifest: cannot get manifest: could not find def file for distro bluefin-42

I'm guessing it has to do with what we use as base image

[dosubot]

Hi, @kervin5. I'm Dosu, and I'm helping the image-template team manage their backlog and am marking this issue as stale.

Issue Summary:

• You reported that the build-iso workflow fails due to a missing manifest for the distro "bazzite-42" after changing the repo name in iso.toml.
• Other users have experienced similar issues with different distro names like "bluefin-42."
• The problem seems related to how the ISO builder recognizes the distro and whether it identifies it as Fedora.
• The root cause appears to be tied to the distro definition files and the ISO builder's handling of custom distro names.
• The issue remains unresolved with no recent updates or fixes.

Next Steps:

• Please let me know if this issue is still relevant with the latest version of the image-template repository by commenting here.
• If I do not hear back within 7 days, this issue will be automatically closed.

Thank you for your understanding and contribution!