From 41a417fc69de4861530835609cc04fc930a87ed2 Mon Sep 17 00:00:00 2001 From: Ihor Dvoretskyi Date: Sun, 17 Apr 2016 23:12:49 -0700 Subject: [PATCH] Updated container removing command Updated container removing command - added "force" option to delete running containers as well. --- 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 a232afe86b..95c7c52ba8 100644 --- a/docs/getting-started-guides/docker.md +++ b/docs/getting-started-guides/docker.md @@ -160,7 +160,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 rm $(docker ps -aq)`, note this removes _all_ containers running under Docker, so use with caution. +You may use `docker rm -f $(docker ps -aq)`, note this removes _all_ containers running under Docker, so use with caution. 2. Cleanup the filesystem: