Gitlab Runner custom helper image registry.
Status update - Runner PM (2022-12-29)
- We do not plan to implement this feature as it will add too much complexity to the Runner.
- The current solution is to override the helper image
Proposal
With Gitlab 14.0 the Gitlab-runner feature flag FF_GITLAB_REGISTRY_HELPER_IMAGE=true
became the default which tries to download a helper image from registry.gitlab.com
This is a problem for us because most of our runners have no internet access and this will fail.
At the moment we can easily configure our dockerhub mirror to the docker daemon.json as the default registry and the runner pulls every image from our internal cache. This doesn't work anymore because the new image URL has a specific registry in the URL/name and so it won't use the default registry.
I know that we can set the feature flag FF_GITLAB_REGISTRY_HELPER_IMAGE
to false but now every user needs to change his gitlab-runner config because of that. And is it possible that you may won't publish the helper images anymore to dockerhub in the near future or that you may remove the feature flag in the near future?
Would it maybe possible to add a new configuration to the gitlab runner where we can configure our internal registry URL and you only append the helper image name?
Config example:
default_docker_registry=<my_internal_registry>
Default value:
default_docker_registry=registry.gitlab.com
Which will lead to a generated URL inside the gitlab runner like:
$default_docker_registry/gitlab-org/gitlab-runner/gitlab-runner-helper:x86_64-c1edb478