Allow for cross-architecture ISO builds

bcross commented 9 months ago

What steps did you take and what happened: I clicked the "Build ISO" button on the "Registration Endpoint" page.

What did you expect to happen: I expected a bootable ISO to be created.

Anything else you would like to add: An ISO is created, but the contents of the EFI/BOOT folder only contains BOOTAA64.EFI instead of bootx64.efi and is not bootable on a amd64 system. I assume this is because my Kubernetes cluster is running on arm64. It would be great to be able to generate bootable ISOs for amd64 on an arm64 Kubernetes cluster.

Environment:

Elemental release version (use cat /etc/os-release): 1.3
Rancher version: 2.8 (arm64)
Kubernetes version (use kubectl version): v1.27.9+k3s1 (arm64)
Cloud provider or hardware configuration: k3s in OCI VMs

kkaempf commented 9 months ago

Thanks for reporting this. I adapted the title and added it to our backlog.

kkaempf commented 8 months ago

See rancher/elemental-operator#600

frelon commented 5 months ago

FYI cross-arch ISO builds were implemented in https://github.com/rancher/elemental-operator/pull/728

The issue tracking this feature for the ui is https://github.com/rancher/elemental-ui/issues/181

rancher / elemental

Allow for cross-architecture ISO builds #1170