Build multi-architecture container images with Docker Build Cloud
Introduction
Setup and build images with Docker Build Cloud
Use GitHub Actions with Docker Build Cloud
Next Steps
Build multi-architecture container images with Docker Build Cloud
Who is this for?
This is an introductory topic for software developers who want to learn how to use Docker Build Cloud.
What will you learn?
Upon completion of this Learning Path, you will be able to:
- Build Arm images and multi-architecture images with Docker Build Cloud
- Use GitHub Actions to automate image builds
Prerequisites
Before starting, you will need the following:
- A computer with Docker installed. This can be Windows, macOS, or Linux. Any architecture can be used.
- A GitHub account
- A Docker Hub account
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
You’ll build multi-architecture container images for Arm and x86 using Docker Build Cloud and then automate those builds with GitHub Actions. You’ll compare common approaches for multi-architecture builds and configure Docker Build Cloud as the builder to avoid relying on instruction emulation. Then, you’ll create a GitHub repository, add a workflow that targets multiple architectures, and set required secrets so the workflow can run unattended. By triggering a cloud-backed build, you’ll see logs that confirm Arm and x86 variants were produced through the configured pipeline.
Frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Use Docker Build Cloud as the builder. Emulation can be slow, so you’ll configure cloud-backed builds instead.
Check the build or workflow logs for the listed target platforms and verify the image manifest with Docker tooling. You should see entries for both Arm and x86.
Confirm that all required secrets are added in the repository settings and that the workflow references them by the correct names. Update the secret names or values to match the workflow.
The steps use a new repository to get started, but you can use an existing one. Ensure the workflow file and required secrets are added to whichever repository you choose.
Review the workflow configuration and logs to see that the selected builder is Docker Build Cloud. Ensure the builder is set before the build step runs.