Packages for distributions that are not on the list are currently not available from our package repository. You can
install
them manually by downloading the RPM package from our S3 bucket.
In GitLab 14.7 and later, a FIPS 140-2 compliant version of GitLab Runner is
available for RHEL distributions. You can install this version by using
gitlab-runner-fips as the package name, instead of gitlab-runner.
To install a specific version of GitLab Runner:
For DEB based systems:
apt-cache madison gitlab-runner
sudo apt-get install gitlab-runner=10.0.0
For RPM based systems:
yum list gitlab-runner --showduplicates | sort-rsudo yum install gitlab-runner-10.0.0-1
With package signing, each package is signed when it’s built. So until you can trust
the build environment and the secrecy of the used GPG key, the valid signature on the package
will prove that its origin is authenticated and its integrity was not violated.
Packages signing verification is enabled by default only in some of the DEB/RPM based distributions,
so users wanting to have this kind of verification may need to adjust the configuration.
GPG keys used for packages 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.
The public key package that should be installed is named
gpg-pubkey-35dfa027-60ba0235
.
The repository file for RPM based distributions will be 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).
In GitLab Runner 12.10 we’ve added support for a special
variable -
GITLAB_RUNNER_DISABLE_SKEL
- that when set to
true
is preventing usage of
skel
when creating the
$HOME
directory of the newly created user.
Starting with GitLab Runner 14.0
GITLAB_RUNNER_DISABLE_SKEL
is being set to
true
by default.
If for any reason it’s needed that
skel
directory will be used to populate the newly
created
$HOME
directory, the
GITLAB_RUNNER_DISABLE_SKEL
variable should be set explicitly
to
false
before package installation. For example:
Shell configuration added to the $HOME directory with the usage of skel may
interfere with the job execution and introduce unexpected problems like the ones mentioned above.
If you didn't find what you were looking for,
search the docs
.
If you want help with something specific and could use community support,
post on the GitLab forum
.
For problems setting up or using this feature (depending on your GitLab
subscription).
