mirror of
https://github.com/matze/wastebin.git
synced 2026-04-25 08:36:00 +03:00
[GH-ISSUE #192] Dockerfile: build failure on arm64 hosts #113
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/wastebin-matze#113
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @zenofile on GitHub (Dec 13, 2025).
Original GitHub issue: https://github.com/matze/wastebin/issues/192
The build fails on arm64 hosts because it uses a zig binary for the wrong architecture:
@matze commented on GitHub (Dec 13, 2025):
Which is to be expected because the dockerfile is supposed to be used for x86_64 hosts only. I don't have an aarch64 host which is why I will use it that way to build future images.
Can I close this issue? It should I add some clarification into the dockerfile and/or readme?
@zenofile commented on GitHub (Dec 13, 2025):
That is unfortunate. You can close the issue.
@matze commented on GitHub (Dec 13, 2025):
I use Docker not podman but what exactly is the issue of building an aarch64 image on an x86_64 host with the
--target arm64or--target x86_64option?@zenofile commented on GitHub (Dec 13, 2025):
Just an inconvenience, not a real issue. Since you removed
Dockerfile.arm, I mistakenly assumed the main Dockerfile should also work on aarch64 hosts, but you made it clear now that this wasn't the intention.@matze commented on GitHub (Dec 13, 2025):
I think for "real" (whatever that means) portable Dockerfile's we could eschew of the
--targetflag during thecargobuild. But that would mean for me to build with QEMU which is unbearably slow.