From f27d9f983cada7dd2e638a8bc5169e94f9d64ac8 Mon Sep 17 00:00:00 2001 From: Kevin Monk Date: Thu, 19 Jan 2017 14:52:50 +0000 Subject: [PATCH] redeploying should not use existing volume --- .../deploy-app/12_data_management_with_volumes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docker-cloud/getting-started/deploy-app/12_data_management_with_volumes.md b/docker-cloud/getting-started/deploy-app/12_data_management_with_volumes.md index 783cd19a16..ee0d2cf255 100644 --- a/docker-cloud/getting-started/deploy-app/12_data_management_with_volumes.md +++ b/docker-cloud/getting-started/deploy-app/12_data_management_with_volumes.md @@ -23,7 +23,7 @@ If you `redeploy` the Redis service you created earlier, you'll see that the cou Let's try that. First, redeploy the redis service to reset the counter. ```bash -$ docker-cloud service redeploy redis +$ docker-cloud service redeploy redis --not-reuse-volumes ``` Check the container status using the `container ps` command, and wait until the new container is running again. In the example below you can see the original container in the "Terminated" state, and the new container that is "Starting".