Question 1

How do I speed up Run-On-Arch builds?

Accepted Answer

Use the githubToken parameter to cache Docker images in your project's GitHub Package Registry, and leverage the install parameter to pre-install dependencies. However, ensure no secrets are exposed in the cached image layer.

Question 2

Run-On-Arch vs self-hosted runners for ARM testing: which should I use?

Accepted Answer

Run-On-Arch is easier to set up and manage within GitHub Actions for multi-arch support, but self-hosted runners offer native performance. Choose Run-On-Arch for convenience and broad architecture coverage; opt for self-hosted if build speed is critical.

Question 3

Can I use Run-On-Arch for Windows ARM testing?

Accepted Answer

No, Run-On-Arch currently only supports Linux distributions as listed in the supported platforms table. For Windows ARM, you would need native GitHub runners or self-hosted alternatives.

Question 4

How to handle segmentation faults in Run-On-Arch?

Accepted Answer

Update to version 3.0.0 or later, as the README notes this release addresses sporadic segmentation faults. Ensure your workflow uses @v3 to mitigate these CI failures.

Question 5

How do I specify a custom base image in Run-On-Arch?

Accepted Answer

Set arch and distro to 'none' and use the base_image parameter with the Docker image name, e.g., '--platform=linux/riscv64 riscv64/ubuntu:24.04'. Be aware of the caching limitation for multiple custom images in a workflow.

Question 6

Does Run-On-Arch support RISC-V?

Accepted Answer

Yes, it supports riscv64 with distros like Ubuntu 20.04/22.04/24.04 and Alpine Edge, as shown in the supported platforms table, making it useful for testing on emerging architectures.

Run your job on another architecture: arm32, aarch64 and others

What is Run your job on another architecture: arm32, aarch64 and others?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions