Run CircleCI Arm Native Workflows on a SUSE Arm GCP VM
Introduction
Get started with CircleCI on Google Axion C4A
Create a Google Axion C4A Arm virtual machine on GCP
Install CircleCI
Create a resource class
Install CircleCI Machine Runner on SUSE Arm
Build and test an Arm64 Node.js app using CircleCI
Next Steps
Run CircleCI Arm Native Workflows on a SUSE Arm GCP VM
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.
During creation, select the
c4a-standard-4 machine type in the Google Cloud Console. After launch, open the VM details in Compute Engine and verify the machine type shows c4a-standard-4.The CLI should be available to validate configuration files, run jobs locally, and manage runners. If it can’t be installed or used, recheck that the required repositories were added to the SUSE environment as shown in the steps.
Use the CircleCI organization (namespace) where your project workflows run. The resource class links your self-hosted runner to that namespace so only authorized jobs can target the VM.
Check the CircleCI web dashboard for the resource class and runner status. On the VM, the runner setup completes with a connection to CircleCI and then waits for jobs that reference its resource class.
Configure the job to use the custom resource class created for the Arm runner. When triggered, the job runs on the SUSE arm64 VM and the CircleCI UI shows the job associated with that resource class.