summaryrefslogtreecommitdiffstats
path: root/playbooks/aws/BUILD_AMI.md
diff options
context:
space:
mode:
authorOpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com>2017-11-14 22:46:08 -0800
committerGitHub <noreply@github.com>2017-11-14 22:46:08 -0800
commit32493153d4c5714ff3c5a04e2497be8f92cba4de (patch)
tree1f6cab0367caf6a7963c2075c977de0638f859dc /playbooks/aws/BUILD_AMI.md
parentec564267f4a25036c92a71be481cfd9e4c03537a (diff)
parent68b66faed0a5fc4364e50daa5e4a9a1b42a12734 (diff)
downloadopenshift-32493153d4c5714ff3c5a04e2497be8f92cba4de.tar.gz
openshift-32493153d4c5714ff3c5a04e2497be8f92cba4de.tar.bz2
openshift-32493153d4c5714ff3c5a04e2497be8f92cba4de.tar.xz
openshift-32493153d4c5714ff3c5a04e2497be8f92cba4de.zip
Merge pull request #6102 from mgugino-upstream-stage/fix-docker-reg-auth-proxy
Automatic merge from submit-queue. 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 'playbooks/aws/BUILD_AMI.md')
0 files changed, 0 insertions, 0 deletions