summaryrefslogtreecommitdiffstats
path: root/roles/etcd/templates/etcd.docker.service
diff options
context:
space:
mode:
authorDevan Goodwin <dgoodwin@redhat.com>2016-06-14 10:24:59 -0300
committerDevan Goodwin <dgoodwin@redhat.com>2016-06-14 10:27:54 -0300
commita7b4676ee4a5388efc8b801a79c62e5e7627c467 (patch)
treec63a989e1892dc4b941da144a29d2d53fa898a7c /roles/etcd/templates/etcd.docker.service
parentfea08b9ba213b69667e103ff9dfd4383218e9eac (diff)
downloadopenshift-a7b4676ee4a5388efc8b801a79c62e5e7627c467.tar.gz
openshift-a7b4676ee4a5388efc8b801a79c62e5e7627c467.tar.bz2
openshift-a7b4676ee4a5388efc8b801a79c62e5e7627c467.tar.xz
openshift-a7b4676ee4a5388efc8b801a79c62e5e7627c467.zip
Attempt to fix containerized node start failure with Docker 1.10.
It appears that in some situations (can't reliably reproduce yet), node will fail to start. This appears to be related to the node-dep service and possibly it's environment file. This file is also an EnvironmentFile for the node service, but it's only created by the node-dep service, and it looks like it may try to read it's environment before the node-dep service has fully started and created the file. Workaround with a an explicit service start.
Diffstat (limited to 'roles/etcd/templates/etcd.docker.service')
0 files changed, 0 insertions, 0 deletions