From 18ad8a7a718629f841206912f87e810724d24258 Mon Sep 17 00:00:00 2001 From: Doug Davis Date: Tue, 26 Apr 2016 11:08:01 -0700 Subject: [PATCH] Add missing -f to "docker rm" Signed-off-by: Doug Davis --- 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 c5fe830da5..3295987e7b 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: