I am running a local gitlab-runner as a docker container:
docker run -d --name gitlab.com-runner --restart always \
-v /srv/gitlab.com-runner/config:/etc/gitlab-runner \
-v /var/run/docker.sock:/var/run/docker.sock \
gitlab/gitlab-runner:latest
I registered the runner with a specific group on gitlab.com like this:
docker run --rm -t -i \
-v /srv/gitlab.com-runner/config:/etc/gitlab-runner \
--name gitlab.com-runner-registration \
gitlab/gitlab-runner:latest register \
--non-interactive \
--executor "docker" \
--docker-image alpine:3 \
--url "https://gitlab.com/" \
--registration-token "MY_GROUP_REG_TOKEN" \
--description "docker-runner" \
--tag-list "docker" \
--run-untagged \
--locked="false"
Then I disabled the use of shared runners for that group in an effort to force it to use this locally running gitlabl-runner. Unfortunately, I only saw this output from the gitlab-runner when a job should have started to run:
2018-10-23T07:42:59.358770721Z ERROR: Failed to load config stat /etc/gitlab-runner/config.toml: no such file or directory builds=0
2018-10-23T07:43:02.359968362Z Configuration loaded builds=0
2018-10-23T09:44:11.685735340Z WARNING: Checking for jobs... failed runner=29950a87 status=couldn't execute POST against https://gitlab.com/api/v4/jobs/request: Post https://gitlab.com/api/v4/jobs/request: net/http: TLS handshake timeout
The pipeline appears stalled and no log output is shown on gitlab.com. Is there any way I could get more info to get to the source of this problem?