[X] The documentation does not mention anything about my problem
[X] There are no open or closed issues that are related to my problem
Description
I want to use an actual Dockerfile to build a binary, using the platforms parameter and outputs: type=local....
In my dockerfile, I use the multiarch feature to build the binary and copy it in a target FROM scratch.
When I run it locally using docker buildx build --platform linux/arm64,linux/amd64 --target binary --output type=local,dest=$(pwd), it creates 2 directories, linux_amd64 and linux_arm64 in which I find the binaries. With this gh action, I only get a single binary.
Contributing guidelines
I've found a bug, and:
Description
I want to use an actual Dockerfile to build a binary, using the
platforms
parameter andoutputs: type=local...
. In my dockerfile, I use the multiarch feature to build the binary and copy it in a targetFROM scratch
. When I run it locally usingdocker buildx build --platform linux/arm64,linux/amd64 --target binary --output type=local,dest=$(pwd)
, it creates 2 directories,linux_amd64
andlinux_arm64
in which I find the binaries. With this gh action, I only get a single binary.Expected behaviour
With this configuration
I'd expect to find
$GITHUB_WORKSPACE/linux_amd64/my-binary
and$GITHUB_WORKSPACE/linux_arm64/my-binary
but I only get$GITHUB_WORKSPACE/my-binary
.Actual behaviour
With this configuration
I only get
$GITHUB_WORKSPACE/my-binary
.Repository URL
https://github.com/jdrouet/git-metrics
Workflow run URL
https://github.com/jdrouet/git-metrics/actions/runs/9250622026/job/25444518546
YAML workflow
Workflow logs
See https://github.com/jdrouet/git-metrics/actions/runs/9250622026/job/25444518546
BuildKit logs
No response
Additional info
No response