You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am successfully using the multi-arch capabilities to build images for both amd64 and arm64, however not when using an image obtained through registry-image with IMAGE_ARG_* as introduced in #52 (we need it as the image is in ECR/private). It apparently uses the host arch for the base image regardless of target arch.
Small reproducer. For good measure I use oci-build-image from master tag, currently 1aac28e to get the latest buildkit updates - same result with v0.11.0:
Dockerfile:
ARG from_image=golang:1.19.5-alpine3.16
FROM ${from_image}
RUN echo test
#9 [linux/arm64 2/2] RUN echo test
#0 0.084 .buildkit_qemu_emulator: /bin/sh: Invalid ELF image for this architecture
#9 ERROR: process "/dev/.buildkit_qemu_emulator /bin/sh -c echo test" did not complete successfully: exit code: 255
------
> [linux/arm64 2/2] RUN echo test:
#0 0.084 .buildkit_qemu_emulator: /bin/sh: Invalid ELF image for this architecture
If I remove the parts about IMAGE_ARG_*, it just works.
I am successfully using the multi-arch capabilities to build images for both amd64 and arm64, however not when using an image obtained through
registry-image
withIMAGE_ARG_*
as introduced in #52 (we need it as the image is in ECR/private). It apparently uses the host arch for the base image regardless of target arch.Small reproducer. For good measure I use oci-build-image from
master
tag, currently 1aac28e to get the latest buildkit updates - same result with v0.11.0:Dockerfile:
Pipeline:
Relevant output:
If I remove the parts about
IMAGE_ARG_*
, it just works.Tagging @vito as the author of #52 and @rdrgmnzs as the author of multi-arch support (567071e).
The text was updated successfully, but these errors were encountered: