-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build fails with no useful error message when using iso-bios format on arm64 architecture #3930
Comments
Thanks for the reply @deitch, I appreciate it! Yeah, I would have expected to be able to produce an amd64 image regardless of the architecture of my host machine. I can work around for now by building images on a different machine. |
If you feel like figuring out how to make it work and open a PR, that would be great. In the meantime, can you change the topic of this issue to reflect that building iso-bios doesn't work on arm64? |
furious-luke
changed the title
Build fails with no useful error message when using iso-bios format
Build fails with no useful error message when using iso-bios format on arm64 architecture
Jun 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Building the "getty" example from the examples directory produces an error when specifying
iso-bios
as the format. I'm running on an Apple M2 Max, Ventura 13.3.1 (a). I've installed the latest version of Linuxkit via thego install
command. Querying the version returns:Steps to reproduce the issue:
go install github.com/linuxkit/linuxkit/src/cmd/linuxkit@latest
getty.yml
containing the contents of the LinuxKit reporsitory'sexamples/getty.yml
.linuxkit build -format iso-bios getty.yml
Describe the results you received:
Describe the results you expected:
I would expect the correct ISO image to be produced without error.
Additional information you deem important (e.g. issue happens only occasionally):
This same command works as expected on my Arch Linux machine.
The text was updated successfully, but these errors were encountered: