Troubleshooting GitLab Runner

dns = ["192.168.xxx.xxx","192.168.xxx.xxx"]

I’m seeing x509: certificate signed by unknown authority

For more information, see the self-signed certificates .

I get Permission Denied when accessing the /var/run/docker.sock

If you want to use Docker executor, and you are connecting to Docker Engine installed on server. You can see the Permission Denied error. The most likely cause is that your system uses SELinux (enabled by default on CentOS, Fedora and RHEL). Check your SELinux policy on your system for possible denials.

Docker-machine error: Unable to query docker version: Cannot connect to the docker engine endpoint.

This error relates to machine provisioning and might be due to the following reasons:

• There is a TLS failure. When docker-machine is installed, some certificates might be invalid. To resolve this issue, remove the certificates and restart the runner:

  sudo su -
  rm -r /root/.docker/machine/certs/*
  service gitlab-runner restart

  After the runner restarts, it registers that the certificates are empty and recreates them.

• The hostname is longer than the supported length in the provisioned machine. For example, Ubuntu machines have a 64 character limit for HOST_NAME_MAX . The hostname is reported by docker-machine ls . Check the MachineName in the runner configuration and reduce the hostname length if required.

dialing environment connection: ssh: rejected: connect failed (open failed)

This error occurs when the Docker autoscaler cannot reach the Docker daemon on the target system when the connection is tunneled through SSH. Ensure that you can SSH to the target system and successfully run Docker commands, for example docker info .

Adding an AWS Instance Profile to your autoscaled runners

After you create an AWS IAM Role, in your IAM console, the role has a Role ARN and a Instance Profile ARNs . You must use the Instance Profile name, not the Role Name .

Add the following value to your [runners.machine] section: "amazonec2-iam-instance-profile=<instance-profile-name>",

The Docker executor gets timeout when building Java project

This most likely happens, because of the broken aufs storage driver: Java process hangs on inside container . The best solution is to change the storage driver to either OverlayFS (faster) or DeviceMapper (slower).

Check this article about configuring and running Docker or this article about control and configure with systemd .

I get 411 when uploading artifacts

This happens due to fact that GitLab Runner uses Transfer-Encoding: chunked which is broken on early version of NGINX ( https://serverfault.com/questions/164220/is-there-a-way-to-avoid-nginx-411-content-length-required-errors ).

Upgrade your NGINX to newer version. For more information see this issue: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/1031

I am seeing other artifact upload errors, how can I further debug this?

Artifacts are uploaded directly from the build environment to the GitLab instance, bypassing the GitLab Runner process. For example:

• With the Docker executor, uploads occur from the Docker container
• With the Kubernetes executor, uploads occur from the build container in the build pod

The network route from the build environment to the GitLab instance might be different from the GitLab Runner to the GitLab instance route.

To enable artifact uploads, ensure that all components in the upload path allow POST requests from the build environment to the GitLab instance.

By default, the artifact uploader logs the upload URL and the HTTP status code of the upload response. This information is not enough to understand which system caused an error or blocked artifact uploads. To troubleshoot artifact upload issues, enable debug logging for upload attempts to see upload response’s headers and body.

If uploads reach GitLab but fail with an error status code (for example, produces a non-successful response status code), investigate the GitLab instance itself. For common artifact upload issues, see GitLab documentation .

No URL provided, cache will not be download / uploaded

This error occurs when the GitLab Runner helper receives an invalid URL or does not have any pre-signed URLs to access a remote cache. Review each cache-related config.toml entry and provider-specific keys and values. An invalid URL might be constructed from any item that does not follow the URL syntax requirements.

Additionally, ensure that your helper image and helper_image_flavor match and are up-to-date.

If there is a problem with the credentials configuration, a diagnostic error message is added to the GitLab Runner process log.

Error: warning: You appear to have cloned an empty repository.

When running git clone using HTTP(s) (with GitLab Runner or manually for tests) and you see the following output:

$ git clone https://git.example.com/user/repo.git
Cloning into 'repo'...
warning: You appear to have cloned an empty repository.

Failed to load config Invalid OffPeakPeriods value: open /usr/local/go/lib/time/zoneinfo.zip: no such file or directory

# on Debian/Ubuntu based systems
sudo apt-get install tzdata
# on RPM based systems
sudo yum install tzdata
# on Linux Alpine
sudo apk add -U tzdata

sealert -a /var/log/audit/audit.log

ERROR: Error cleaning up pod: Unauthorized
ERROR: Error cleaning up secrets: Unauthorized
ERROR: Job failed (system failure): Unauthorized