From 1fac9952481cd3ee0bb288b4189a9220ab243361 Mon Sep 17 00:00:00 2001
From: Matthias Radestock <matthias.radestock@gmail.com>
Date: Sat, 13 Sep 2014 07:51:06 +0100
Subject: [PATCH] work around 'docker rm -f' weirdness I've been seeing

~# docker rm -f weave
Error response from daemon: Cannot destroy container weave: Driver devicemapper failed to remove root filesystem 29e46c3e400ee3c8654f2b06a0f6d97bde98dfeb9bb61d25195dba38c04324fc: Device is Busy

whereas the corresponding two-step 'docker kill' + 'docker rm' works
fine.
---
 weaver/weave | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/weaver/weave b/weaver/weave
index 5dab5d9b..503144aa 100755
--- a/weaver/weave
+++ b/weaver/weave
@@ -152,9 +152,10 @@ case "$COMMAND" in
         exit 0
         ;;
     stop)
-        if ! docker rm -f weave >/dev/null 2>&1 ; then
+        if ! docker kill weave >/dev/null 2>&1 ; then
             echo "Weave is not running."
         fi
+        docker rm -f weave >/dev/null 2>&1 || true
         if command_exists conntrack
         then
             conntrack -D -p udp --dport 6783 >/dev/null 2>&1