Explore related resources

Find more information about the topics in this Learning Path:

Give feedback

How would you rate this Learning Path?

Review frequently asked questions

AI-assisted

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.

Close
?
Which runner executor should I use for this pipeline?
Use the Docker executor to run containerized builds on GitLab‑hosted runners. This path configures jobs to run on arm64 by adding the Arm64 runner tag in .gitlab-ci.yml.
How do I target arm64 runners in `.gitlab-ci.yml`?
Add the Arm64 runner tag to the job’s tags section in .gitlab-ci.yml. Jobs that include this tag are scheduled on GitLab‑hosted arm64 runners.
How do I confirm my job actually ran on Arm64?
Open the job log and review the lscpu output. The reported architecture should indicate Arm64, confirming that the job executed on the intended runner.
What result should I expect after the pipeline runs?
You should see successful build and push stages, with logs showing the C program compilation and container image creation. The new image and tag appear in the project’s GitLab Container Registry.
What should I check if the image is not in the GitLab Container Registry?
Verify that the push stage finished without errors in the job log. Then open the project’s Container Registry page and confirm the expected image tag is listed.

Share

Tell others about this Learning Path.

Back