I’m using GitLab deployed on Kubernetes using the official Helm chart, version 11.9.0
I have two private projects A and B. A builds and pushes a docker image to the internal container registry. Project B then uses that image as its CI container. However, this results in ERROR: Job failed: image pull failed: Back-off pulling image
.
I read in the docs that GitLab runner can automatically authenticate with the internal registry, so this should work. This is the gitlab-ci.yml I’m using for project B:
foo:
image: $CI_REGISTRY/project-a:bar
script: ...
This is the log output from the task:
Running with gitlab-runner 11.8.0 (4745a6f3)
on gitlab-gitlab-runner-7b9576474b-t45pk yf_hmeGJ
Using Kubernetes namespace: default
Using Kubernetes executor with image <registry>/project-a:bar ...
Waiting for pod default/runner-yfhmegj-project-1-concurrent-0msc8v to be running, status is Pending
Waiting for pod default/runner-yfhmegj-project-1-concurrent-0msc8v to be running, status is Pending
Waiting for pod default/runner-yfhmegj-project-1-concurrent-0msc8v to be running, status is Pending
Waiting for pod default/runner-yfhmegj-project-1-concurrent-0msc8v to be running, status is Pending
Waiting for pod default/runner-yfhmegj-project-1-concurrent-0msc8v to be running, status is Pending
Waiting for pod default/runner-yfhmegj-project-1-concurrent-0msc8v to be running, status is Pending
ERROR: Job failed: image pull failed: Back-off pulling image "<registry>/project-a:bar"
Is this use case not supported or am I missing some configuration?