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
?
How do I know the job ran on an Arm-hosted runner?
Check the Actions run details for the runner name or labels that indicate an Arm architecture and confirm the workflow selects the Arm-hosted runner. If the run shows a different runner, review the runs-on setting in the workflow.
I’m using a private repository and can’t select an Arm-hosted runner—what should I check?
Confirm the account uses a Team or Enterprise Cloud plan because private repositories require it for Arm-hosted runners. If it still doesn’t appear, review the repository or organization runner settings.
Which build approach does this path use for multiple architectures?
The path explains emulation and manifest-based builds, then uses Arm-hosted runners to perform native arm64 builds and assemble a multi-architecture image. The workflow relies on native Arm execution rather than instruction emulation for the arm64 build.
Where do I store credentials so the workflow can push images to Docker Hub?
Add the required registry credentials as repository secrets and reference them in the workflow. Without these secrets, the push step fails to authenticate.
What result should I expect after the workflow completes?
Expect a successful Actions run and a new image tag on Docker Hub with a multi-architecture manifest listing arm64 and amd64. If the platforms are missing, review the build logs to see which architecture jobs ran and which images were pushed.

Share

Tell others about this Learning Path.