FlyCI macOS Runners Hardware
FlyCI is built to provide fastest and cheapest macOS runners for GitHub Actions. We focus on macOS to deliver the most exceptional service for our users.
The bare metal machines we use are fast M2 Mac Minis. The M2s have 8 CPU cores, 10 GPU cores, 16G RAM, 1TB SSD and 10GB network bandwidth.
Runner Labels
FlyCI uses runner labels to allow choosing from different hardware configurations. The labels determine the operating system, vCPU count, RAM and storage. The labels are used in jobs.[job-name].runs-on property in the workflow config.
| Processor/OS | vCPU | RAM | Runner Label |
|---|---|---|---|
| M2 / macOS 13 | 4 | 7GB | flyci-macos-large-latest-m2 |
| M2 / macOS 13 | 8 | 14GB | flyci-macos-xlarge-latest-m2 |
| M2 / macOS 14 | 4 | 7GB | flyci-macos-14-m2 |
| M2 / macOS 14 | 8 | 14GB | flyci-macos-14-xlarge-m2 |
All runners provide 28GB storage.
Note
M1 runner labels listed below are deprecated. They are automatically mapped to the corresponding M2 runners.
| Processor/OS | vCPU | RAM | Runner Label (DEPRECATED) |
|---|---|---|---|
| M1 / macOS 13 | 4 | 7GB | flyci-macos-large-latest-m1 |
| M1 / macOS 13 | 8 | 14GB | flyci-macos-xlarge-latest-m1 |
| M1 / macOS 14 | 4 | 14GB | flyci-macos-14-m1 |
| M1 / macOS 14 | 8 | 14GB | flyci-macos-14-xlarge-m1 |
Nested Virtualization
Due to limitations from Apple, nested virtualization is currently not supported. This means that you cannot start a VM in the FlyCI runner. So, running Docker↗, Colima↗ and similar is not possible for the moment.
M2 and M3 chips include ARM 8.4 FEAT_NV2 (enhanced nested virtualization support). However, support for that is still not available in the Apple's Virtualization Framework.