Skip to content

The runner image

Every label runs the same image: Ubuntu 24.04 with the GitHub Actions runner, the Docker CLI, which uses the VM’s Docker, and the apt packages GitHub’s ubuntu-24.04 runners have, not their language toolchains, cloud CLIs or browsers. It’s built from a public Dockerfile and signed, and each backmesh release names one image by its digest.

  • The apt packages GitHub’s Ubuntu 24.04 image installs, from the list in GitHub’s runner-images repository: compilers and build tools (gcc, g++, make, autoconf, pkg-config), archive tools (zip, unzip, 7z, xz, zstd), network tools (curl, wget, ssh, rsync, dig), jq, shellcheck, sqlite3, xvfb and the rest. backmesh follows GitHub’s list as it changes.
  • git, Git LFS and the GitHub CLI, gh.
  • The Docker CLI with Buildx and Compose, using the VM’s Docker.
  • Node.js 22 with npm, and Yarn and pnpm through Corepack.
  • Python 3 with pipx.
  • kubectl, helm, yq and envsubst.

GitHub’s image also preinstalls language toolchains, cloud CLIs, browsers and databases. backmesh’s doesn’t, which keeps the image small enough for every job to pull it on its own VM. Coming from ubuntu-latest lists them with the setup action for each.

A job gets a language at the version it asks for from that language’s setup action, as it does on GitHub’s runners:

steps:
- uses: actions/setup-node@v6
with:
node-version: 24
- uses: actions/setup-python@v6
with:
python-version: '3.13'

actions/setup-go, actions/setup-java, actions/setup-dotnet, ruby/setup-ruby and the other setup actions work the same way. Each job’s VM is new, so the action downloads its version in every job.

When a run: step calls a command the image doesn’t have, and a package in Ubuntu’s archive provides it, the step installs that package with apt and goes on, with one line in its log:

backmesh: installing ruby for ruby

The Azure, Google Cloud and AWS CLIs install on first use from each vendor’s signed packages.

apt checks the package against the archive’s signature. A typo, or a command no Ubuntu package provides, fails as usual with command not found. The first use in a job takes a few seconds longer. To pin a version, or to install the package before you need it, install it in a step of its own:

- run: sudo apt-get install -y ruby-full

The image ships without apt’s package lists, so the first apt command in a job fetches them; an apt-get update of your own works too.

First-use install works for commands a bash step runs itself, as run: steps do by default. A command started by another program, such as a tool a Makefile or a Python script calls, isn’t installed; install its package in an earlier step. Neither is a command in a shell: sh step or in a job’s container:.

For tools Ubuntu doesn’t package, or to match another image completely, run the job in a container image that has them, with GitHub’s container:. The job’s steps then run inside that image, on the job’s own VM:

jobs:
build:
runs-on: backmesh-4
container: mcr.microsoft.com/dotnet/sdk:9.0

Any image works, including one you build with exactly the tools your jobs need. Each job’s VM is new, so it pulls the image in every job.