Closed liyimeng closed 1 year ago
Hello @liyimeng
You are setting a random flavor name, so when framework tries to include the packages it tries searc hing for the given flavor in the profiles, but alpine is not a valid falvor.
You should use either alpine-opensuse-leap
or alpine-ubuntu
as the ---FLAVOR
to get an apline iso.
You can seea ll supported out of the box flavors to build with earthly under https://github.com/kairos-io/kairos/blob/master/framework-profile.yaml
Hello @liyimeng
You are setting a random flavor name, so when framework tries to include the packages it tries searc hing for the given flavor in the profiles, but alpine is not a valid falvor.
You should use either
alpine-opensuse-leap
oralpine-ubuntu
as the---FLAVOR
to get an apline iso.
@Itxaka thanks! In this case, the we probably need to update document at https://kairos.io/docs/development/development/, where it is misleading, what do u think?
@Itxaka by the way, even using alpine-ubuntu, it fails as well. since package grub-bios
is not available on arm64 in alpine3.18
I re-open this issue, hope it is OK with u
Hi @liyimeng ,
yeah, for arm64 isos, we have only tested opensuse-leap as its the only one that works out of the box. For other flavors, the only supported arm64 devices is rpi3/rpi4.
Are you building an generic arm64 iso for an arm machine?
I will send a patch to install grub-bios only under the x86 arch in the alpine image, as this is still an issue :)
Hello @liyimeng You are setting a random flavor name, so when framework tries to include the packages it tries searc hing for the given flavor in the profiles, but alpine is not a valid falvor. You should use either
alpine-opensuse-leap
oralpine-ubuntu
as the---FLAVOR
to get an apline iso.@Itxaka thanks! In this case, the we probably need to update document at kairos.io/docs/development/development, where it is misleading, what do u think?
Indeed this is an issue, we never updated the docs to show the current state of arm building.
Basically to build a generic arm iso (generic means its not tied to a device like a rpi4) you need to run a different target (earthly +all-arm-generic --FLAVOR=$FLAVOR
) and also we dont mark that that has only been tested to work with opensuse-leap and under a VM in arm64 platforms, so not even on real hardware (is there any arm64 dev boxes out there?)
Will also update the docs to mention this. Thanks for the heads up!
it seem the build was not that reproducible. I try a couple of flavours. The one most close to succeed is alpine-ubuntu on amd64, it fails like this
+framework | FLAVOR=alpine-ubuntu
+framework | --> RUN luet cleanup --system-target /framework
+framework | ERROR Error on removing 02
+framework | ERROR Earthfile line 269:4
+framework | The command
+framework | RUN luet cleanup --system-target /framework
+framework | did not complete successfully. Exit code 2
================================== ❌ FAILURE ===================================
+framework *failed* | Repeating the failure error...
+framework *failed* | FLAVOR=alpine-ubuntu
+framework *failed* | --> RUN luet cleanup --system-target /framework
+framework *failed* | ERROR Error on removing 02
+framework *failed* | ERROR Earthfile line 269:4
+framework *failed* | The command
+framework *failed* | RUN luet cleanup --system-target /framework
+framework *failed* | did not complete successfully. Exit code 2
🛰️ Reuse cache between CI runs with Earthly Satellites! 2-20X faster than without cache. Generous free tier https://cloud.earthly.dev
Kairos version:
master/v2.4.1
CPU architecture, OS, and Version:
ARM64
Describe the bug
I try to build kairos on master/v2.4.1 branch, it fails at building the framework. Not sure what I have been missing To Reproduce
earthy.sh +iso --FLAVOR=alpine
Expected behavior
Logs
================================== ❌ FAILURE ===================================