Deal with reboot of the underlying machine

[bboreham]

If you have the weave container running and reboot the underlying machine, then Docker restarts the container but it sits there saying 'Waiting for interface ethwe to come up'.

'weave status' says nothing at all.

'weave launch' says "Weave is already running."

'weave stop' does stop the container, at which point you can run 'weave launch' again successfully.

Obviously if the network bridge isn't up then the weave router can't do very much, but it seems wrong that the only way to make progress is to stop it and start it again

[bboreham]

The problem is not just the weave router; any other containers which use the weave network will also suffer if they are restarted by Docker without 'weave launch' having set up the necessary network interfaces, bridge, nat rules, etc.

The recommended thing seems to be to run the Docker daemon with -r=false as described here https://docs.docker.com/articles/host_integration/, and have some higher-level process to run all the right scripts on reboot.

[rade]

I reckon the weave router should stop if the interface doesn't come up within, say, 5 seconds. That addresses the 'weave status/launch' weirdness.

As for the application containers... we should document the behaviour and proposed approach in a sub-section of https://github.com/zettio/weave#troubleshooting