Configure Master Provisioning to pull from an internal repository rather than dockerhub.
Using private repositories in Master provisioning as a workaround for Docker Hub Rate Limiting
- CloudBees CI (CloudBees Core)
- CloudBees CI (CloudBees Core) on modern cloud platforms - Managed Master
- CloudBees CI (CloudBees Core) on modern cloud platforms - Operations Center
When configuring images used for master provisioning the default behaviour is to pull the image from Cloudbees public dockerhub repository. However in certain situations Cloudbees CI administrators
may want to pull images from an internal repository instead. For example using internal image repository allows administrators a workaround for Docker Hub Rate Limitingintroduced recently.
Currently the master provisioning page does not provide a field for an imagepullsecret which is required when using private repositories. Below workaround will help overcome that limitation and allow administrators to
use private repositories.
A workaround will be to add below to YAML field under
$JENKINS_URL/masterProvisioning/ or (Manage Jenkins –> Configure Master Provisioning). Replace
my-secret-1 with your configured image secret name.
--- kind: StatefulSet spec: template: spec: imagePullSecrets: - name: "my-secret-1"