- FAQ
- 1. Where are logs stored for service?
- 2. Run in --debug mode
- 3. I get a PathTooLongException during my builds on Windows
- a) Use Git with core.longpaths enabled
- b) Use NTFSSecurity tools for PowerShell
- 4. I'm seeing x509: certificate signed by unknown authority
- 5. I get Permission Denied when accessing the /var/run/docker.sock
- 6. The Docker executor gets timeout when building Java project.
- 7. I get 411 when uploading artifacts.
FAQ
1. Where are logs stored for service?
- If the GitLab Runner is run as service on Linux/OSX the daemon logs to syslog.
- If the GitLab Runner is run as service on Windows it logs to System's Event Log.
--debug
mode
2. Run in Is it possible to run GitLab Runner in debug/verbose mode. Do it from terminal:
gitlab-runner --debug run
3. I get a PathTooLongException during my builds on Windows
This is caused by tools like npm
which will sometimes generate directory structures
with paths more than 260 characters in length. There are two possible fixes you can
adopt to solve the problem.
a) Use Git with core.longpaths enabled
You can avoid the problem by using Git to clean your directory structure, first run
git config --system core.longpaths true
from the command line and then set your
project to use git fetch from the GitLab CI project settings page.
b) Use NTFSSecurity tools for PowerShell
The NTFSSecurity PowerShell module provides a Remove-Item2 method which supports long paths. The Gitlab CI Multi Runner will detect it if it is available and automatically make use of it.
x509: certificate signed by unknown authority
4. I'm seeing Please See the self-signed certificates
Permission Denied
when accessing the /var/run/docker.sock
5. I get 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.
6. 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.
7. I get 411 when uploading artifacts.
This happens due to fact that runner uses Transfer-Encoding: chunked
which is broken on early version of Nginx (http://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-ci-multi-runner/issues/1031