Skip to main content
Each job runs in a fresh VM built from a Debian image with Node.js, npm, Python and git. Each section says which actions and jobs were verified on Coreload runners in our benchmark runs; use them in your workflow as you do today, with runs-on set to the label we sent you. Other actions may work too; they aren’t verified yet. Other setup-* actions that fetch Ubuntu builds may fail the same way as Python’s (see below).

​
Node.js

Node.js and npm are preinstalled. Verified: actions/checkout and actions/setup-node.

​
pnpm and Turborepo

Verified: pnpm/action-setup, and a whole pnpm and Turborepo job.

​
Go

Go is not preinstalled. Verified: actions/setup-go; add it before any step that runs go.

​
Rust

Rust is not preinstalled. Verified: a Rust job that installs it and runs cargo build and cargo test.

​
Python

Debian’s own Python is preinstalled; our benchmark runs didn’t exercise it. actions/setup-python failed for the CPython versions our benchmark runs tried (the quickstart lists them) when it downloaded them, because those builds are made for Ubuntu only. Keep a job that needs a particular Python version on its current runner for now. Coming: the image GitHub’s hosted Ubuntu runners use, where setup-python works. (coming soon)

​
Caching

actions/cache works (restore and save), as on any self-hosted runner. There is no Coreload cache for customer jobs yet; see Caching.

​
Docker

Docker is not available in jobs yet: a step that runs docker, a job’s container: and its services: fail. Keep those jobs on their current runner for now. Coming: Docker in every job. (coming soon)