Limitations
What RaftRun doesn't do yet. Check this before you move a workflow.
If a job needs one of these, keep it where it runs today. Everything else can move with a one-line change.
Runners
- No Windows or macOS runners. Jobs that need runs-on: windows-* or macos-* have to stay on GitHub-hosted runners or another provider.
- No Arm64 or GPU runners. Every runner is x64 without a GPU. Builds for Arm64 can cross-compile or use QEMU emulation, which is slower.
- Up to 16 vCPU and 32 GB of memory. There are no 32 or 64 vCPU sizes. Memory is 2 GB per vCPU, half of what some other providers give at the same vCPU count.
- 20 GB of disk on the three smallest sizes. Jobs that pull large images or build big artifacts should use raft-ubuntu-24.04-4 (40 GB) or larger.
- Ubuntu 24.04 only, no custom images. Each job starts from the same Ubuntu 24.04 image. Bringing your own image, or older Ubuntu releases, is not supported yet.
- Caching covers actions/cache and Rust builds. There is no Docker layer cache yet, and the actions/cache integration is in beta. Rust builds are cached through mbx.
- Egress rules apply to IPv4. With a deny-all default, IPv6 is blocked outright. A job running as root can change the rules, so treat them as a guard rail, not a sandbox.
- No static outbound IP addresses. Runner machines do not have fixed IPs, so you cannot allowlist RaftRun in a firewall by address.
- GitHub.com only. GitHub Enterprise Server is not supported.
Docker hosts
- No public addresses. Published ports are reachable only through an SSH port forward. See Open a service.
- The build cache needs the host's cache to survive a stop. Compose builds in a folder set up with Use in a folder use it by themselves; plain
docker buildneeds two flags. See Keep the build cache. - No bind mounts from your laptop. A bind mount uses the host's disk. Sync your files in instead; see Use your local files.
- x64 only. Arm64 images run only through emulation.