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
The documentation does not mention anything about my problem
There are no open or closed issues that are related to my problem
Description
Background
We haven't changed anything with our pipelines and have been using:
- name: Set up QEMU
uses: docker/setup-qemu-action@v3
Successfully. After upgrading our EKS cluster to version 1.30 I started noticing that the support platforms were saying they were getting installed but now the "Extracting available platforms" only shows the original two from the node.
We haven't changed anything with our self hosted github runner container either and it worked previously as well.
Expected behaviour
When running the step with:
with:
platforms: arm64,arm
I expect it to install those platforms and make them available.
Actual behaviour
As a test I ran with:
- name: Set up QEMU
uses: docker/setup-qemu-action@v3
with:
platforms: arm64,arm
And the output is:
Installing QEMU static binaries
/usr/local/bin/docker run --rm --privileged docker.io/tonistiigi/binfmt:latest --install arm64,arm
installing: arm64 OK
installing: arm OK
{
"supported": [
"linux/amd64",
"linux/arm64",
"linux/386",
"linux/arm/v7",
"linux/arm/v6"
],
"emulators": [
"qemu-aarch64",
"qemu-arm"
]
}
Extracting available platforms
linux/amd64,linux/386
as you can see from the above output I would expect arm64 and arm to be listed as the available platforms.
Is there a gotcha I should be aware of? The image tonistiigi/binfmt:latest hasn't been updated in quite some time, so I doubt that the issue is from there 🤷 .
Repository URL
No response
Workflow run URL
No response
YAML workflow
name: Test workflow
on:
push:
paths:
- "*"
jobs:
dev-main:
runs-on: [self-hosted, dev]
steps:
- name: Check out repository code
uses: actions/checkout@v4
with:
fetch-depth: 0
- name: Set up QEMU
uses: docker/setup-qemu-action@v3
with:
platforms: arm64,arm
Workflow logs
Successfully checks out the code. I'm including the "failed" step from qemu install:
Circling back around to this. Has there been any recent findings?
EDIT: I spent today debugging this and was able to get multi arch images to start building by doing this (NOTE: In the example here the --install all can probably be replaced with --install arm64,arm):
docker run --rm --privileged multiarch/qemu-user-static --reset -p yes --install all
docker buildx create --platform linux/amd64,linux/arm64 --driver=docker-container --name=multiarchbuilder --use --bootstrap
docker buildx use multiarchbuilder
echo "---------"
docker buildx ls
echo "---------"
Contributing guidelines
I've found a bug, and:
Description
Background
We haven't changed anything with our pipelines and have been using:
Successfully. After upgrading our EKS cluster to version 1.30 I started noticing that the support platforms were saying they were getting installed but now the "Extracting available platforms" only shows the original two from the node.
We haven't changed anything with our self hosted github runner container either and it worked previously as well.
Expected behaviour
When running the step with:
I expect it to install those platforms and make them available.
Actual behaviour
As a test I ran with:
And the output is:
as you can see from the above output I would expect
arm64
andarm
to be listed as the available platforms.Is there a gotcha I should be aware of? The image
tonistiigi/binfmt:latest
hasn't been updated in quite some time, so I doubt that the issue is from there 🤷 .Repository URL
No response
Workflow run URL
No response
YAML workflow
Workflow logs
Successfully checks out the code. I'm including the "failed" step from qemu install:
BuildKit logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: