Docker not configured to pull from undercloud registry by default
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Steven Hardy |
Bug Description
I enabled logging requests from the undercloud registry like this:
[root@undercloud /]# cat /etc/docker-
version: 0.1
log:
accesslog:
disabled: false
fields:
service: registry
storage:
cache:
layerinfo: inmemory
filesystem:
http:
addr: 192.168.24.1:8787
Then I did docker pull from the undercloud, and some deployed overcloud nodes - they hit dockerhub without trying the local registry AFAICT. I assume we're passing the registry location explicitly in the heat hook (are we?! I've yet to re deploy with logging enabled), but it'd be good if we made manual operations also use the local registry where possible.
The option to do this seems to be:
--add-registry=
I also wonder if, at least optionally, we should block dockerhub so we can be sure all the images are actually pulled to the local registry e.g in CI, otherwise we may be taking a performance hit without realizing? There's a --block-registry option that does this I think.
Changed in tripleo: | |
status: | New → Triaged |
milestone: | none → pike-2 |
tags: | added: containers |
Changed in tripleo: | |
importance: | Undecided → Medium |
Actually in my environment during an overcloud there's no access to the undercloud registry recorded at all AFAICS.