Kubernetes runner fails with config error
Summary
A kubnernetes gitlab-runner cluster installed using gitlab was running fine on Friday. Sometime over the weekend the containers started failing.
PANIC: Near line 5 (last key parsed 'runners.docker'): bare keys cannot contain ':'
Steps to reproduce
I wish I knew. The runner was working on Friday. Over the weekend the system now exhibits this problem.
Actual behavior
The runner fails to execute. The container is being continually restarted.
Expected behavior
The runner should be executing.
Relevant logs and/or screenshots
mWARNING: Running in user-mode.
mWARNING: The user-mode requires you to manually start builds processing:
mWARNING: $ gitlab-runner run
mWARNING: Use sudo for system-mode:
mWARNING: $ sudo gitlab-runner...
PANIC: Near line 5 (last key parsed 'runners.docker'): bare keys cannot contain ':'
mWARNING: Running in user-mode.
Environment description
Kubernetes runner installed on Google Cloud using the gitlab interface.
How does one view the configuration file of an instance that is not running? How to access the instance when it panics trying to get started? So many questions. Not enough answers.
Used GitLab Runner version
Please run and paste the output of
gitlab-runner --version
. If you are using a Runner where you don't have access to, please paste at least the first lines the from build log, like:Running with gitlab-ci-multi-runner 1.4.2 (bcc1794) Using Docker executor with image golang:1.8 ...
Sure? How do I do that with a kubernetes runner? I can't even connect to the runner because it keeps failing to start.