From 0d595bf95ab0118c2d5dae9bf23d0a365b54746b Mon Sep 17 00:00:00 2001 From: Ihor Dvoretskyi Date: Wed, 6 Apr 2016 17:27:35 -0700 Subject: [PATCH] Changed container removing command Changed `docker kill` to `docker rm` as completely cleaning solution for this case. --- docs/getting-started-guides/docker.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started-guides/docker.md b/docs/getting-started-guides/docker.md index afcb4f63e7..275d92fd00 100644 --- a/docs/getting-started-guides/docker.md +++ b/docs/getting-started-guides/docker.md @@ -150,7 +150,7 @@ See [here](/docs/getting-started-guides/docker-multinode/deployDNS/) for instruc Many of these containers run under the management of the `kubelet` binary, which attempts to keep containers running, even if they fail. So, in order to turn down the cluster, you need to first kill the kubelet container, and then any other containers. -You may use `docker kill $(docker ps -aq)`, note this removes _all_ containers running under Docker, so use with caution. +You may use `docker rm $(docker ps -aq)`, note this removes _all_ containers running under Docker, so use with caution. 2. Cleanup the filesystem: