We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In all examples I always see this action used like this:
- name: Set up QEMU uses: docker/setup-qemu-action@v3 - name: Set up Docker Buildx uses: docker/setup-buildx-action@v3
But if I omit this action, and just use:
- name: Set up Docker Buildx uses: docker/setup-buildx-action@v3
I can still build ARM64 images using QEMU via Buildx.
So what is the exact purpose of this action? Was it something that was needed in the past and now has become obsolete?
The text was updated successfully, but these errors were encountered:
Also curious to see an answer here 🙏
Sorry, something went wrong.
If you need to build an image for a platform that is not supported by buildkit, you can configure QEMU and virtualize it. https://github.com/docker/buildx#building-multi-platform-images
Supported virtual platforms: https://wiki.qemu.org/Documentation/Platforms
No branches or pull requests
Description
In all examples I always see this action used like this:
But if I omit this action, and just use:
I can still build ARM64 images using QEMU via Buildx.
So what is the exact purpose of this action? Was it something that was needed in the past and now has become obsolete?
The text was updated successfully, but these errors were encountered: