- Supported distributions
- Install GitLab Runner
- Upgrade GitLab Runner
- GPG signatures for package installation
- Troubleshooting
Install GitLab Runner using the official GitLab repositories
To install GitLab Runner, you can use a package from the GitLab repository.
Supported distributions
GitLab provides packages for the following supported versions of Linux distributions with Packagecloud. New runner deb
or rpm
packages for new OS distribution releases are added automatically when supported by Packagecloud.
Depending on your setup, other Debian or RPM based distributions may also be supported. This refers to distributions that are derivative of a supported GitLab Runner distribution and that have compatible package repositories. For example, Deepin is a Debian derivative. So, the runner deb
package should install and run on Deepin. You may also be able to install GitLab Runner as a binary
on other Linux distributions.
Distribution | Support Information |
---|---|
Debian | https://wiki.debian.org/LTS |
Ubuntu | https://wiki.ubuntu.com/Releases |
LinuxMint | https://linuxmint.com/download_all.php |
Raspbian | |
RHEL | https://access.redhat.com/product-life-cycles?product=Red%20Hat%20Enterprise%20Linux |
Oracle Linux | https://endoflife.date/oracle-linux |
Fedora | https://docs.fedoraproject.org/en-US/releases/eol/ |
Amazon Linux | https://aws.amazon.com/linux/ |
Install GitLab Runner
To install GitLab Runner:
-
Add the official GitLab repository:
Debian/Ubuntu/Mintcurl -L "https://packages.gitlab.com/install/repositories/runner/gitlab-runner/script.deb.sh" | sudo bash
RHEL/CentOS/Fedora/Amazon Linuxcurl -L "https://packages.gitlab.com/install/repositories/runner/gitlab-runner/script.rpm.sh" | sudo bash
-
Install the latest version of GitLab Runner, or skip to the next step to install a specific version:
Theskel
directory usage is disabled by default to preventNo such file or directory
job failures.Debian/Ubuntu/Mintsudo apt install gitlab-runner
RHEL/CentOS/Fedora/Amazon Linuxsudo yum install gitlab-runner or sudo dnf install gitlab-runner
A FIPS 140-2 compliant version of GitLab Runner is available for RHEL distributions. You can install this version by usinggitlab-runner-fips
as the package name, instead ofgitlab-runner
. -
To install a specific version of GitLab Runner:
Debian/Ubuntu/Mintapt-cache madison gitlab-runner sudo apt install gitlab-runner=17.2.0-1
RHEL/CentOS/Fedora/Amazon Linuxyum list gitlab-runner --showduplicates | sort -r sudo yum install gitlab-runner-17.2.0-1
After completing the above steps, a runner can be started and can be used with your projects!
Make sure that you read the FAQ section which describes some of the most common problems with GitLab Runner.
Upgrade GitLab Runner
To install the latest version of GitLab Runner:
sudo apt update
sudo apt install gitlab-runner
sudo yum update
sudo yum install gitlab-runner
GPG signatures for package installation
The GitLab Runner project provides two types of GPG signatures for the package installation method:
Repository metadata signing
To verify that the package information downloaded from the remote repository can be trusted, the package manager uses repository metadata signing.
The signature is verified when you use a command like apt-get update
, so the
information about available packages is updated before any package is downloaded and
installed. Verification failure should also cause the package manager to reject the
metadata. This means that you cannot download and install any package from the repository
until the problem that caused the signature mismatch is found and resolved.
GPG public keys used for package metadata signature verification are installed automatically on first installation done with the instructions above. For key updates in the future, existing users need to manually download and install the new keys.
We use one key for all our projects hosted under https://packages.gitlab.com. You can find the details about the key used in the Linux package documentation. This documentation page lists also all keys used in the past.
Package signing
Repository metadata signing proves that the downloaded version information originates at https://packages.gitlab.com. It does not prove the integrity of the packages themselves. Whatever was uploaded to https://packages.gitlab.com - authorized or not - is properly verified until the metadata transfer from repository to the user was not affected.
With package signing, each package is signed when it’s built. Until you can trust the build environment and the secrecy of the used GPG key, you cannot verify package authenticity. A valid signature on the package proves that its origin is authenticated and its integrity was not violated.
Package signing verification is enabled by default only in some of the Debian/RPM based distributions. To use this type of verification, you might need to adjust the configuration.
GPG keys used for package signature verification can be different for each of the repositories hosted at https://packages.gitlab.com. The GitLab Runner project uses its own key pair for this type of the signature.
RPM-based distributions
The RPM format contains a full implementation of GPG signing functionality, and thus is fully integrated with the package management systems based upon that format.
You can find the technical description of how to configure package signature verification for RPM-based distributions in the Linux package documentation. The GitLab Runner differences are:
- The public key package that should be installed is named
gpg-pubkey-35dfa027-60ba0235
. - The repository file for RPM-based distributions is named
/etc/yum.repos.d/runner_gitlab-runner.repo
(for the stable release) or/etc/yum.repos.d/runner_unstable.repo
(for the unstable releases). - The package signing public key can be imported from https://packages.gitlab.com/runner/gitlab-runner/gpgkey/runner-gitlab-runner-49F16C5CC3A0F81F.pub.gpg.
Debian-based distributions
The deb
format does not officially contain a default and included method for signing packages.
The GitLab Runner project uses the dpkg-sig
tool for signing and verifying signatures on packages. This
method supports only manual verification of packages.
To verify a deb
package:
-
Install
dpkg-sig
:apt update && apt install dpkg-sig
-
Download and import the package signing public key:
curl -JLO "https://packages.gitlab.com/runner/gitlab-runner/gpgkey/runner-gitlab-runner-49F16C5CC3A0F81F.pub.gpg" gpg --import runner-gitlab-runner-49F16C5CC3A0F81F.pub.gpg
-
Verify downloaded package with
dpkg-sig
:dpkg-sig --verify gitlab-runner_amd64.deb Processing gitlab-runner_amd64.deb... GOODSIG _gpgbuilder 931DA69CFA3AFEBBC97DAA8C6C57C29C6BA75A4E 1623755049
If a package has an invalid signature or signed with an invalid key (for example a revoked one), the output is similar to the following:
dpkg-sig --verify gitlab-runner_amd64.deb Processing gitlab-runner_amd64.deb... BADSIG _gpgbuilder
If the key is not present in the user’s keyring, the output is similar to:
dpkg-sig --verify gitlab-runner_amd64.v13.1.0.deb Processing gitlab-runner_amd64.v13.1.0.deb... UNKNOWNSIG _gpgbuilder 880721D4
Current GPG public key
Download the current public GPG key used for package signing from https://packages.gitlab.com/runner/gitlab-runner/gpgkey/runner-gitlab-runner-49F16C5CC3A0F81F.pub.gpg.
Key Attribute | Value |
---|---|
Name | GitLab, Inc.
|
support@gitlab.com
| |
Fingerprint | 931D A69C FA3A FEBB C97D AA8C 6C57 C29C 6BA7 5A4E
|
Expiry | 2025-04-25
|
release.sha256
files for the S3 releases
available in the <https://gitlab-runner-downloads.s3.dualstack.us-east-1.amazonaws.com>
bucket.Previous GPG public keys
Keys used in the past can be found in the table below.
For keys that were revoked, it’s highly recommended to remove them from the package signing verification configuration.
Signatures made by the following keys should not be trusted anymore.
Sl. No. | Key Fingerprint | Status | Expiry Date | Download (revoked keys only) |
---|---|---|---|---|
1 | 3018 3AC2 C4E2 3A40 9EFB E705 9CE4 5ABC 8807 21D4
| revoked
| 2021-06-08
| revoked key |
2 | 09E5 7083 F34C CA94 D541 BC58 A674 BF81 35DF A027
| revoked
| 2023-04-26
| revoked key |
Troubleshooting
Here are some tips on troubleshooting and resolving issues when installing GitLab Runner.
Error: No such file or directory
job failures
Sometimes the default skeleton (skel
) directory
causes issues for GitLab Runner, and it fails to run a job.
See issue 4449 and
issue 1379.
To avoid this, when you install GitLab Runner, a gitlab-runner
user is
created, and by default, the home directory is created without any skeleton in
it. Shell configuration added to the home directory with the usage of skel
may interfere with the job execution.
This configuration can introduce unexpected problems like the ones mentioned above.
If you had created the runner before the avoidance of skel
was made
the default behavior, you can try removing the following dotfiles:
sudo rm /home/gitlab-runner/.profile
sudo rm /home/gitlab-runner/.bashrc
sudo rm /home/gitlab-runner/.bash_logout
If you need to use the skel
directory to populate the newly
created $HOME
directory, you must set the GITLAB_RUNNER_DISABLE_SKEL
variable explicitly
to false
before you install the runner:
export GITLAB_RUNNER_DISABLE_SKEL=false; sudo -E apt-get install gitlab-runner
export GITLAB_RUNNER_DISABLE_SKEL=false; sudo -E yum install gitlab-runner