search

CiscoCloud / haproxy-consul

Dynamic haproxy configuration using consul
Apache License 2.0
168 stars 85 forks source link

Container does not restart properly after running "docker stop" #25

Closed kcraft closed 8 years ago

kcraft commented 8 years ago

Runnung docker stop haproxy-consul followed by docker start haproxy-consul results in the following error in the logs:

ln: /consul-template/template.d/haproxy.tmpl: File exists

It looks like this line in launch.sh needs to remove the link before creating it or needs to test for the existence of the link:

ln -s /consul-template/template.d/${HAPROXY_MODE}.tmpl /consul-template/template.d/haproxy.tmpl

The same problem happens if the docker daemon or the VM it runs on are restarted.

arhea commented 8 years ago

+1 we have encountered this as well.

chazsconi commented 8 years ago

I believe this is fixed by my PR https://github.com/CiscoCloud/haproxy-consul/pull/27

BrianHicks commented 8 years ago

Should be fixed by #27. Thanks @chazsconi!