Runner Types

Runners in IronCD provide isolated virtual machines where jobs execute. Each runner type defines a number of CPUs and base operating system. This page describes the naming convention for runner labels and outlines what’s preinstalled on each image.

Runner Labels

Runners are identified by a label of the format:


ironcd-<N>cpu-<os>

where each segment means:

Segment	Description	Example
`ironcd`	Indicates a standard IronCD VM runner.	`ironcd`
`<N>cpu`	Number of virtual CPUs allocated to the runner.	`2cpu`, `4cpu`, `8cpu`
`ubuntu-2404`	Base operating system image and version.	`ubuntu-2404`

Usage in GitHub Actions Pipelines

Runners are selected per job via the runs-on key in your workflow file. Set runs-on to a valid label to select an IronCD runner.


# .github/workflows/example.yml
jobs:
  build:
    runs-on: ironcd-4cpu-ubuntu-2404
    steps:
      - run: make build

Available Runners

Details about the available runners are below. IronCD periodically updates the runner images to ensure they are up-to-date with the latest security patches and software versions.

Ubuntu

Label	vCPUs	Memory	OS
`ironcd-2cpu-ubuntu-2404`	2	8GB	Ubuntu 24.04 LTS
`ironcd-4cpu-ubuntu-2404`	4	16GB	Ubuntu 24.04 LTS
`ironcd-8cpu-ubuntu-2404`	8	32GB	Ubuntu 24.04 LTS

System Details

Ubuntu 24.04 LTS base
Ubuntu PRO and ESM disabled
APT configured to use HTTPS transport only
Builds run the actions user. actions has passwordless sudo access

Installed Software

curl
git
jq
build-essential
ca-certificates
wget
qemu-guest-agent
unzip
htop
rsync
bzip2
gnupg
software-properties-common
pkg-config
libicu74
liblttng-ust1
libyaml-dev
libssl-dev
zlib1g
docker-ce
docker-ce-cli
containerd.io
docker-buildx-plugin
docker-compose-plugin

Docker

Docker comes pre-installed, and is configured to start at boot. The actions user is a member of the docker group and does not require sudo to perform Docker operations.