Runner configuration

Add cracicorp/setup@v1 before a job’s other steps to select its runner resources, image, reusable template, and network policy. You can omit the action to use your organization’s default runner configuration.

- uses: cracicorp/setup@v1
  with:
    size: "4"
    image: default

The selected template replaces these built-in defaults. An explicit size, image, or network input then overrides that part of the template for the current job.

Input names are case-insensitive. Values may use GitHub Actions expressions when the expression resolves to a scalar value available before the job starts.

Organization administrators create runner templates under Settings → Runner Templates. Select one by its slug:

- uses: cracicorp/setup@v1
  with:
    template: release-build

The selected template supplies the base image, size, and network policy.

Without a template input, CRACI selects the built-in default template.

Set size to the number of compute units required by the job. Values outside the supported 1..32 range are invalid.

- uses: cracicorp/setup@v1
  with:
    size: "8"

Quote the value to keep it unambiguously a string in workflow YAML.

Set image to a supported image name:

- uses: cracicorp/setup@v1
  with:
    image: craci-ubuntu-24.04

See Runner images for image names, architectures, and installed software.

Set network to a YAML block when a job needs a policy different from the selected runner template:

- uses: cracicorp/setup@v1
  with:
    network: |
      default: deny
      presets: [github, npm]

See Control network access from jobs for policy defaults, built-in presets, custom package sources, and connection rules.

CRACI validates runner configuration before starting the job. If CRACI cannot parse an input, it schedules the default runner environment and writes a warning to the job log. An unknown image or runner template is rejected instead of being silently replaced. Check the job log and correct the setup input before relying on the requested configuration.