Coreload: GitHub Actions runners Limits

Who can use Coreload

• GitHub organizations only. Personal accounts aren't supported yet.
• Private repositories only, chosen when you install the App. Jobs from public repositories don't run on Coreload.

What a job gets

• One fresh VM per job. It never serves a second job, and it is destroyed when the job ends.
• One Coreload label per job; see Runners and labels.
• A Debian (bookworm) image with Node.js, npm, Python and git, not yet GitHub's Ubuntu image. Docker is not available in jobs yet (so container: and services: can't start), setup actions that download Ubuntu-only builds may fail (actions/setup-python does, for the CPython versions it downloads), and some standard tools, such as Go and Rust, aren't preinstalled: install them in the job. See What runs today. GitHub's Ubuntu image, with Docker and the standard toolchains. coming soon

Network

• Outbound traffic is limited per VM and per machine, and outbound mail ports are refused.
• A job's traffic leaves from addresses other customers share, which can change. Never put them in an IP allow list. Authenticate your job's requests at your own service instead.
• Organizations that depend on an IP allow list aren't supported yet.

Not allowed

Mining cryptocurrency, running proxies, VPN or Tor exits, sending unsolicited mail, scanning or attacking systems without their owner's permission, and getting around the isolation between VMs. A job that does any of these is stopped, and the organization may be suspended.