Browse Source

use-buildset-registry: configure as a pull-through proxy

Docker has a curious behavior with respect to the registry-mirror
setting: it will only use the credentials for dockerhub itself.
Therefore, configure the buildset registry to be a pull-through
cache for dockerhub, but with no credentials, so that we can set
buildset registry credentials under the dockerhub url without
their actually being used for dockerhub.

Change-Id: I5daf93868d408d71cf2766fbe1bb17f2cfa8a3c7
changes/12/638312/1
James E. Blair 3 months ago
parent
commit
c8c439e0d8
1 changed files with 3 additions and 0 deletions
  1. 3
    0
      roles/run-buildset-registry/tasks/main.yaml

+ 3
- 0
roles/run-buildset-registry/tasks/main.yaml View File

@@ -73,6 +73,9 @@
73 73
       REGISTRY_AUTH: htpasswd
74 74
       REGISTRY_AUTH_HTPASSWD_PATH: /auth/htpasswd
75 75
       REGISTRY_AUTH_HTPASSWD_REALM: Registry Realm
76
+      REGISTRY_PROXY_REMOTEURL: https://registry-1.docker.io
77
+      REGISTRY_PROXY_USERNAME:
78
+      REGISTRY_PROXY_PASSWORD:
76 79
     volumes:
77 80
       - "{{ buildset_registry_root}}/data:/var/lib/registry"
78 81
       - "{{ buildset_registry_root}}/certs:/certs"

Loading…
Cancel
Save