# Linux x64 runners

Run eligible GitHub Actions jobs on available Linux x64 runners.

## V1 runner model

Runzivo assigns each eligible GitHub Actions job a fresh Firecracker microVM. The environment is single-use and is destroyed after the job finishes, is cancelled, or cannot continue. A runner is registered with GitHub after a connected, selected repository requests a supported runner configuration.

Every microVM is a cold boot; there is no pre-booted warm pool today. Runner hosts run in Ottawa (YOW) and Montreal (YUL), Canada.

## Runner labels

Available Linux x64 labels are rzv-ubuntu-24.04-x64-2vcpu-8gb, rzv-ubuntu-24.04-x64-4vcpu-16gb, rzv-ubuntu-24.04-x64-6vcpu-24gb, rzv-ubuntu-24.04-x64-8vcpu-32gb, rzv-ubuntu-24.04-x64-16vcpu-64gb, rzv-ubuntu-24.04-x64-32vcpu-128gb. This example uses the 2 vCPU default:

GitHub Actions · runner label

```yaml
runs-on: rzv-ubuntu-24.04-x64-2vcpu-8gb
```

## Capacity and sizes

Runzivo currently supports Linux x64 only. The 2 vCPU, 4 vCPU, 6 vCPU, 8 vCPU, 16 vCPU, 32 vCPU runner sizes are available now.

Run up to your plan's concurrent job limit. Jobs may queue when runner capacity is unavailable. For eligible capacity waits where Runzivo confirms the job never started and no runner resources remain allocated, Runzivo waits up to 900 seconds by default. This platform limit is configurable.

When the wait expires, Runzivo ends the local attempt with zero execution charge, alerts staff, and provides rerun guidance. The attempt does not cancel the GitHub workflow or its sibling jobs.

[Review pricing](https://runzivo.dev/pricing/)

## Docker in jobs

Docker Engine is available in jobs. Jobs can pull images and run containers.

Each job starts with an empty Docker state, because each job runs in a fresh microVM.

The runner image includes Docker Engine 29.1.3, Docker Buildx 0.30.1 and Docker Compose v2 2.40.3, installed from Ubuntu 24.04 packages.

On this page and page tools