When developers push code to GitLab, they can define automated tasks in a .gitlab-ci.yml file. These tasks might include running tests, building applications, or deploying code. GitLab Runner is the application that executes these tasks on computing infrastructure.

gitlab/gitlab-runner:latest is image that can be used to run GitLab Runner in container.

GitLab Runner is the open source project that is used to run your CI/CD jobs and send the results back to GitLab

Download the gitlab-runner Docker image by using the docker pull gitlab/gitlab-runner:<version-tag> command. For the list of available version tags, see GitLab Runner tags.

GitLab Runner runs the CI/CD jobs defined in GitLab.

You can also use the non-interactive mode to use additional arguments to register the runner: ... sudo gitlab-runner register \ --non-interactive \ --url "https://gitlab.com/" \ --token "$RUNNER_TOKEN" \ --executor "docker" \ --docker-image alpine:latest \ --docker-pull-policy "if-not-present" \ --description "docker-runner"

They are responsible for running your builds, tests, deployments, and other CI/CD tasks defined in .gitlab-ci.yml files. The following is a basic workflow of how runners work:

August 13, 2026 - GitLab Runner is the open source project that is used to run your CI/CD jobs and send the results back to GitLab

July 7, 2026 - General purpose CI workers. These Runners execute jobs for a wide range of projects inside the /repos group in GitLab. If access to this kind of Runner is needed, consider moving your git repository to the /repos group and make yourself familiar with the details under Shared GitLab Runners.

January 27, 2025 - Ambassador post by Natalia Granato, CNCF Ambassador GitLab Runner is an open-source application that runs jobs defined in your GitLab CI/CD pipelines.

Official Helm Chart for the GitLab Runner (https://gitlab.com/gitlab-org/gitlab-runner)

This is the repository of the official GitLab Runner written in Go.

This chart deploys a GitLab Runner instance into your Kubernetes cluster.

Register a runner. Install GitLab Runner as a service and start it.

To the right of the runner you want to edit, select Edit ( ). In the Maximum job timeout field, enter a value in seconds. The minimum value is 600 seconds (10 minutes). If not defined, the job timeout for the project is used instead. Select Save changes. To control the amount of time script and after_script runs before it terminates, specify a timeout value in the .gitlab-ci.yml file.

NAME CHART VERSION APP VERSION DESCRIPTION gitlab/gitlab-runner 0.64.0 16.11.0 GitLab Runner gitlab/gitlab-runner 0.63.0 16.10.0 GitLab Runner gitlab/gitlab-runner 0.62.1 16.9.1 GitLab Runner gitlab/gitlab-runner 0.62.0 16.9.0 GitLab Runner gitlab/gitlab-runner 0.61.3 16.8.1 GitLab Runner gitlab/gitlab-runner 0.61.2 16.8.0 GitLab Runner ... Helm chart versions 0.92.2 and later are also available as Open Container Initiative (OCI) artifacts. Use this method as an alternative to adding the GitLab Helm repository.

Index of runner/gitlab-runner/ · / amazon/ debian/ el/ fedora/ linuxmint/ ol/ opensuse/ raspbian/ sles/ ubuntu/

The following commands allow you to manage the runner as a system or user service. Use them to install, uninstall, start, and stop the runner service. ... This command installs GitLab Runner as a service.

Select Create instance runner. Select the operating system where GitLab Runner is installed.

July 23, 2025 - A GitLab Runner is an application that works with GitLab CI/CD to run jobs in a pipeline. When a pipeline is triggered by a code push or a merge request, GitLab sends the jobs to the runner, which executes the defined tasks.