diff options
| author | Michael Gugino <mgugino@redhat.com> | 2017-11-13 13:33:55 -0500 |
|---|---|---|
| committer | Michael Gugino <mgugino@redhat.com> | 2017-11-13 13:33:55 -0500 |
| commit | 68b66faed0a5fc4364e50daa5e4a9a1b42a12734 (patch) | |
| tree | a6153bc2331cf190dd92f911fd9ef1f0157b618b /inventory/byo/hosts.byo.glusterfs.registry-only.example | |
| parent | 7175c6f228f61b883d958c12ba5130f37a0615c4 (diff) | |
| download | openshift-68b66faed0a5fc4364e50daa5e4a9a1b42a12734.tar.gz openshift-68b66faed0a5fc4364e50daa5e4a9a1b42a12734.tar.bz2 openshift-68b66faed0a5fc4364e50daa5e4a9a1b42a12734.tar.xz openshift-68b66faed0a5fc4364e50daa5e4a9a1b42a12734.zip | |
Run registry auth after docker restart
Currently, docker login may fail if a proxy is added to the config
but docker is already running.
This is due to the fact that 'docker login' must have a functioning
docker.service running (with valid network connection) to complete.
Currently, handlers restart the docker service at the end of
the role. This doesn't allow for updating proxy settings before
running docker login.
This commit moves 'docker login' command after flushing handlers.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1511869
Diffstat (limited to 'inventory/byo/hosts.byo.glusterfs.registry-only.example')
0 files changed, 0 insertions, 0 deletions