`weave reset` while using proxy leaves a stopped container behind

[rade]

vagrant@host1:~$ weave launch
vagrant@host1:~$ eval $(weave env)
vagrant@host1:~$ weave reset
WARNING: It appears that your environment is configured to use the Weave Docker API proxy. Stopping it will break this and subsequent docker invocations. To restore your environment, run 'eval $(weave env --restore)'.
Error deleting container: Cannot connect to the Docker daemon. Is the docker daemon running on this host?
vagrant@host1:~$ eval $(weave env --restore)
vagrant@host1:~$ weave reset
vagrant@host1:~$ docker ps -a
CONTAINER ID        IMAGE                         COMMAND                  CREATED             STATUS                      PORTS               NAMES
157c72d557f1        weaveworks/weaveexec:latest   "/home/weave/sigproxy"   36 seconds ago      Exited (1) 35 seconds ago                       berserk_shockley
vagrant@host1:~$ 

[bboreham]

The left-over container is the one that executed the weave script as weave --local reset. It is run with --rm but the Docker client cannot remove it once the proxy has stopped.

Possible ways out:

• don't kill the proxy if DOCKER_HOST is pointing at the proxy
• do docker rm -f from the outer-level script.