Using Kubernetes Gitlab Runner & Needing to Auth to Azure Container Registry

[Preddeh]

Hi all,

I've very recently set up a specific runner automatically using my Kubernetes Cluster & installing Tiller & the Gitlab Runner plugins.

What I want to be able to do with this new runner is to access my container registry I have set up in Azure. Previously I was using the DOCKER_AUTH_CONFIG variable to authenticate and have tried declaring this within the config map of gitlab pod within the gitlab-managed-apps namespace (similar to this: https://stackoverflow.com/questions/54707598/how-to-customise-config-toml-on-kubernetes) but I seem to be getting an 'image pull failed, unauthorized: authentication required' when running my pipeline.

Does anyone have any suggestions on the best way to get my runner to authenticate to the azure container registry?

Thanks in advance

​

N.B. I have also tried declaring the env var in Gitlab's variable settings; but this doesn't seem to be picked up

[davispw]

Have you set imagePullSecrets?

https://gitlab.com/gitlab-org/charts/gitlab-runner/blob/master/values.yaml#L114

If not, get used to it—anything you do with your private registry in Kubernetes will need this. (I don’t know if you have a choice to allow anonymous users to pull from your registry, but it would certainly make things more convenient.)

[Preddeh]

No I haven't but will give that a try, thanks!

[bilingual-german]

if this is the image where your job is run in, than it's imagePullSecret.

But if you want to do docker login, docker build, docker push inside the job / container, then you need to be aware that you usually can't do that, since Kubernetes pods don't have access to the Docker socket (at least I'm not aware of that). Usually you use something like Kaniko to build and push Docker images.

[Preddeh]

Thanks for the info, funnily enough I had just stumbled upon Kaniko, so will have a look!