From 5e1e8ec54341447015316916dba08655f17aa7c3 Mon Sep 17 00:00:00 2001 From: Bryan Boreham Date: Mon, 18 Jan 2016 11:45:17 +0000 Subject: [PATCH] Suggest user disables systemd timeout if using plugin --- site/plugin.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/site/plugin.md b/site/plugin.md index 85ab3b2e..91ece6b8 100644 --- a/site/plugin.md +++ b/site/plugin.md @@ -87,8 +87,17 @@ route, add the `--no-multicast-route` flag to `weave launch-plugin`. We start the plugin with a policy of `--restart=always`, so that it is there after a restart or reboot. If you remove this container (e.g. using `weave reset`) before removing all endpoints created using -`--net=weave`, Docker can -[hang](https://github.com/docker/libnetwork/issues/813). +`--net=weave`, Docker may hang for a long time when it subsequently +tries to talk to the plugin. + +Unfortunately, [Docker 1.9 may also try to talk to the plugin before it has even started it](https://github.com/docker/libnetwork/issues/813). +If using `systemd`, we advise that you modify the Docker unit to +remove the timeout on startup, to give Docker enough time to abandon +its attempts. + +E.g. in the file `/lib/systemd/system/docker.service`, add under `[Service]`: + + TimeoutStartSec=0 [readme]: https://github.com/weaveworks/weave/blob/master/README.md#installation [service-discovery]: weavedns.html