I am trying to build a aarch64 ISO installer image for Fedora. This repository does not support cross building, although it looks like kiwi itself may with --target-arch and "support for the image architecture and binary format on the building host".
--target-arch
I have a aarch64 system, but it is currently running Ubuntu.
It would be nice if there was some documentation for the following:
kiwi-build
.zuul.yaml
fedora-latest
[ ERROR ]: 13:53:08 | KiwiMountKernelFileSystemsError: KiwiCommandError: mount: stderr: mount: /root/fedora-kiwi-descriptions/output-build/build/image-root: permission denied. dmesg(1) may have more information after failed mount system call. , stdout: (no output on stdout)
Probably it needs to be a privileged container of some sort. - Is this repo used for the images on https://fedoraproject.org/workstation/download and if so how does that process work?
I already have a few changes to the README.md and would be happy to contribute any answers into those changes.
This is the issue I'm currently facing on my Ubuntu aarch64 machine.
$ sudo ./kiwi-build --kiwi-file=Fedora.kiwi --image-type=iso --image-profile=Workstation-Live --output-dir=output [ INFO ]: 15:00:45 | Reading runtime config file: '/etc/kiwi.yml' [ INFO ]: 15:00:45 | Loading XML description [ INFO ]: 15:00:45 | Support for XML markup available [ INFO ]: 15:00:46 | --> loaded ./Fedora.kiwi [ INFO ]: 15:00:46 | --> Selected build type: iso [ INFO ]: 15:00:46 | --> Selected profiles: Workstation-Live,GNOME-Desktop,DesktopCommon,LiveInstall,BaseCommon,BootCore [ ERROR ]: 15:00:46 | KiwiRuntimeError: Required tool tagmedia not found in caller environment The attribute 'mediacheck' is set to 'true' which requires the above tool to be installed on the build system
The same command on my x86 Fedora desktop is successful.
You need to edit /etc/kiwi.yml to uncomment and set media_tag_tool to isomd5sum. And you need to install isomd5sum on your system.
/etc/kiwi.yml
media_tag_tool
isomd5sum
Inevitably it was more trouble to try to build on another distribution than booting a Fedora image on my target, even with the fact that it is a low power/performance SBC.
Metadata Update from @philipmolloy: - Issue status updated to: Closed (was: Open)