From 14d78cf08cf6c1fb681944d15a7722884c0cfe58 Mon Sep 17 00:00:00 2001 From: Matthias Radestock Date: Wed, 30 Dec 2015 19:32:04 +0000 Subject: [PATCH 1/2] Update 'reboots' info --- site/troubleshooting.md | 26 ++++++++++++++++---------- 1 file changed, 16 insertions(+), 10 deletions(-) diff --git a/site/troubleshooting.md b/site/troubleshooting.md index b929a803..cc3aecd7 100644 --- a/site/troubleshooting.md +++ b/site/troubleshooting.md @@ -275,18 +275,21 @@ re-connect. ## Reboots -When a host reboots, docker's default behaviour is to restart any -containers that were running. Since weave relies on special network -configuration outside of the containers, the weave network will not -function in this state. +We do not set a restart policy on the Weave router or proxy, because +the process of getting everything re-started and re-connected is not +entirely reliable; we have at least [one issue][issue1556] in Weave +and [one in docker][docker18574] that cause trouble. -To remedy this, stop and re-launch the weave container, and re-attach -the application containers with `weave attach`. +Instead, we recommend you create appropriate startup scripts to launch +weave and run application containers from [your favourite process +manager](systemd.html). -For a more permanent solution, -[disable Docker's auto-restart feature](https://docs.docker.com/articles/host_integration/) -and create appropriate startup scripts to launch weave and run -application containers from your favourite process manager. +If you are shutting down or restarting a host deliberately, run `weave +reset` to clear everything down. + +The Weave Docker plugin does restart automatically, because it must +always start with Docker as described in [its +documentation](plugin.html). ## Snapshot releases @@ -300,3 +303,6 @@ latest snapshot release with Snapshot releases report the script version as "(unreleased version)", and the container image versions as git hashes. + +[issue1556]: https://github.com/weaveworks/weave/issues/1556 +[docker18574]: https://github.com/docker/docker/issues/18574 From 93eef26d0bde03b17e5a66f84ef99f14cb06203e Mon Sep 17 00:00:00 2001 From: Matthias Radestock Date: Wed, 30 Dec 2015 19:38:13 +0000 Subject: [PATCH 2/2] reword --- site/troubleshooting.md | 23 +++++++++-------------- 1 file changed, 9 insertions(+), 14 deletions(-) diff --git a/site/troubleshooting.md b/site/troubleshooting.md index cc3aecd7..23d3b9d1 100644 --- a/site/troubleshooting.md +++ b/site/troubleshooting.md @@ -275,21 +275,19 @@ re-connect. ## Reboots -We do not set a restart policy on the Weave router or proxy, because -the process of getting everything re-started and re-connected is not -entirely reliable; we have at least [one issue][issue1556] in Weave -and [one in docker][docker18574] that cause trouble. - -Instead, we recommend you create appropriate startup scripts to launch -weave and run application containers from [your favourite process -manager](systemd.html). +The router and proxy containers do not have Docker restart policies +set, because the process of getting everything re-started and +re-connected via restart policies is not entirely reliable. Until that +changes, we recommend you create appropriate startup scripts to launch +weave and run application containers from +[your favourite process manager](systemd.html). If you are shutting down or restarting a host deliberately, run `weave reset` to clear everything down. -The Weave Docker plugin does restart automatically, because it must -always start with Docker as described in [its -documentation](plugin.html). +The Weave Docker plugin does restart automatically because it must +always start with Docker, as described in +[its documentation](plugin.html). ## Snapshot releases @@ -303,6 +301,3 @@ latest snapshot release with Snapshot releases report the script version as "(unreleased version)", and the container image versions as git hashes. - -[issue1556]: https://github.com/weaveworks/weave/issues/1556 -[docker18574]: https://github.com/docker/docker/issues/18574