Build multi-architecture images with Buildkite on Google Axion
Introduction
Discover Buildkite on Google Axion C4A instances
Create a Google Axion C4A Arm virtual machine on GCP
Install Buildkite on a Google Axion C4A Arm VM
Set up and connect Buildkite agent on a Google Axion C4A Arm VM
Create a Flask app and set up the Buildkite pipeline
Run the Buildkite pipeline
Next Steps
Build multi-architecture images with Buildkite on Google Axion
Introduction
Discover Buildkite on Google Axion C4A instances
Create a Google Axion C4A Arm virtual machine on GCP
Install Buildkite on a Google Axion C4A Arm VM
Set up and connect Buildkite agent on a Google Axion C4A Arm VM
Create a Flask app and set up the Buildkite pipeline
Run the Buildkite pipeline
Next Steps
Review 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 a Google Axion C4A Arm VM, specifically
c4a-standard-4 with 4 vCPUs and 16 GB memory. You can select either Ubuntu or SUSE Linux Enterprise Server as the OS.Create an agent token in your Buildkite organization after signing in (GitHub sign-in is supported). You use this token during the agent installation and configuration on the C4A VM.
After configuring the agent and queue, check the Agents page in Buildkite; the agent should appear online with the expected queue. If it doesn’t, check the agent configuration and queue name, then repeat the verification step.
Add a Dockerfile and a Python file named
app.py. The provided Dockerfile uses python:3.12-slim, installs Flask, exposes port 5000, and runs the app.A multi-architecture Docker image for Arm and x86 is built with Docker Buildx and pushed to Docker Hub. You then start the containerized Flask application and verify that it runs as the final validation step.