System requirements and supported platforms

Supported operating systems

You can install GitLab Runner on:

• Linux from a GitLab repository or manually
• FreeBSD
• macOS
• Windows
• z/OS

Bleeding-edge binaries are also available.

To use a different operating system, ensure the operating system can compile a Go binary.

Supported containers

You can install GitLab Runner with:

• Docker
• The GitLab Helm chart
• The GitLab agent for Kubernetes
• The GitLab Operator

Supported architectures

GitLab Runner is available for the following architectures:

• x86
• AMD64
• ARM64
• ARM
• s390x
• ppc64le
• riscv64
• loong64

System requirements

The system requirements for GitLab Runner depend on the following considerations:

• Anticipated CPU load of CI/CD jobs
• Anticipated memory usage of CI/CD jobs
• Number of concurrent CI/CD jobs
• Number of projects in active development
• Number of developers expected to work in parallel

For more information about the machine types available for GitLab.com, see GitLab-hosted runners.

FIPS-compliant GitLab Runner

A FIPS 140-2 compliant GitLab Runner is available for the AMD64 architecture. GitLab tests and officially supports this binary on Red Hat Enterprise Linux (RHEL), where it runs against a FIPS 140-2 validated cryptographic library.

The binary can also run on other distributions, but FIPS compliance depends on the OpenSSL module provided by the host operating system. On non-RHEL distributions, GitLab does not validate the cryptographic module. Verify that your operating system provides a FIPS-validated OpenSSL module.

A UBI-8 minimal image is used as the base for creating the GitLab Runner FIPS image.

For more information about using FIPS-compliant GitLab Runner in RHEL, see Switching RHEL to FIPS mode.