Help us learn about your current experience with the documentation. Take the survey.

百度 　　绿地控股集团董事长、总裁张玉良表示，绿地集团高度重视参与雄安新区建设，在对接新区发展定位方面积极努力，促成“雄安绿地双创中心”成为雄安新区首家开业的双创项目。

GitLab Runner runs the CI/CD jobs defined in GitLab. GitLab Runner can run as a single binary and has no language-specific requirements.

For security and performance reasons, install GitLab Runner on a machine separate from the machine that hosts your GitLab instance.

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

System requirements

The system requirements for GitLab Runner depend on the:

• 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 GitLab Runner binary compliant with FIPS 140-2 is available for Red Hat Enterprise Linux (RHEL) distributions and the AMD64 architecture. Support for other distributions and architectures is proposed in issue 28814.

This binary is built with the Red Hat Go compiler and calls into a FIPS 140-2 validated cryptographic library. 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.