Open Gingonic opened 9 years ago
On a separate project I have this as a weave upstart config file -
description "Weave Docker Network Service"
start on started docker
stop on stopping docker
env PEERS="{{ weave_launch_peers }}"
env WEAVE='/usr/local/bin/weave'
pre-start exec ${WEAVE} stop
script
[ -e /etc/default/weave ] && . /etc/default/weave
${WEAVE} launch ${PEERS}
exec /usr/bin/docker logs -f weave
end script
pre-stop exec ${WEAVE} stop
respawn
respawn limit 10 10
kill timeout 10
Which is working OK over there. Can you test that out on your system?
Hi,
on Ubuntu 14.04, the weave executor container is run in a loop and the weave container cannot stick. The problem seems to be the
respawn
command in the /etc/init/weave.conf. As the weave command is simply running a containerfire and forget
style in a new thread upstart will assume the process to be dead.Any thoughts on how to tell upstart that all is good?