I hit on an annoying issue this week, which I’m not sure of the root cause.
Last week I bumped GitLab from 10.6, to 10.8, and somehow broke my GitLab CI Runner.
Somewhere, I have a backup of the config.toml file I was using. I run my GitLab CI Runner in a Docker container. I only run one, as it’s only for my projects. And one is enough.
Somehow, the Runner borked. And annoyingly I neither had a reference of the running version (never use :latest unless you like uncertainty), and recreating without the config.toml file has been a pain.
So for my own future reference, here is my current GitLab Runner config.toml file:
user@8818901c05c8:/# cat /etc/gitlab-runner/config.toml concurrent = 1 check_interval = 0 [[runners]] name = "runner-1" url = "https://my.gitlab.url" token = "{redacted}" executor = "docker" [runners.docker] tls_verify = false image = "docker:dind" privileged = true pull_policy = "if-not-present" disable_cache = false volumes = ["/var/run/docker/sock:/var/run/docker.sock","/cache"] shm_size = 0 [runners.cache] insecure = false
FWIW this isn’t perfect. I’m hitting on a major issue currently whereby GitLab CI Pipeline stages with multiple jobs in the stage are routinely failing. It’s very frustrating. It’s also not scheduled for fix until v11, afaik.