Using Docker Registry Mirror

[jef]

Related: #478

I'm currently using something like this:

image: private-docker-repo.jfrog.io/summerwind/actions-runner:latest
imagePullSecrets:
  - name: docker
dockerRegistryMirror: https://private-docker-repo.jfrog.io

Seems to pull the image fine and also use the mirror fine, but I'm confused on how it's accessing the mirror? How are the credentials sent? I tried looking in the code, but couldn't find it.

This is the closest thing I've found to setting up the mirrors, but not setting the proxy credentials:

https://github.com/actions-runner-controller/actions-runner-controller/blob/30ab0c0b7118d9ae59c186707abc69cb71608574/runner/startup.sh#L31-L33

What am I missing? 😅

[jef]

Never mind, not possible.

moby/moby#30880

[pratikbin]

@Puneeth-n @callum-tait-pbx @mumoshu Question: I have 32 GB 8cpu single node fully dedicated to 2 runners, maybe increase replicas of runners in near future, and I want to use docker registry as pull through cache pod. is it architecturally right or wrong ?

yesterday I deployed registry pod, configured dockerRegistryMirror and ran 1 or 2 workflows, and it was running fine with our docker hub private registry too. haven't got to chance to test it more, and I'm looking forward to using volumeclaimTemplates to mount /var/lib/docker in each runner pod.

[antodoms]

@pratikbalar have you got this working?

[pratikbin]

No, I got other priorities and registry caching was working fine so. But I want to. RunnerSet is a big no for me because of its limitations, https://github.com/actions-runner-controller/actions-runner-controller#stateful-runners

[jef]

Ended up attaching an initContainer and running a script to copy over a Docker config to pass auth.

[Steed-LHV]

Hey mate, do you have any example of the initContianer ? met the same problem

[MatthewRyanRead]

@Steed-LHV I am a little late to this but a good example is #2123 (comment). I personally was using spec.image rather than spec.containers in a template, and for that just moving spec.containers[0].volumeMounts up to spec.volumeMounts did the trick (which is the same as the post two above that one, but I was also using YAML).