From 0d127cdea3b144cf9c9059f15ca0e4b85e3f9a43 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Geeraerts?= <10222438+b-enoit-be@users.noreply.github.com> Date: Mon, 1 Jun 2020 15:12:53 +0200 Subject: [PATCH] A possibly better idea than docker rm Since one could have run `docker-compose up` in the previous, the volume for the database could already exists, but without the `todos` database. Running `docker-compose down --volumes` would fix this (as actually advised in a warning later on. Ref: https://stackoverflow.com/q/61925112/2123530 --- docs_en/tutorial/using-docker-compose/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs_en/tutorial/using-docker-compose/index.md b/docs_en/tutorial/using-docker-compose/index.md index c80c2f8..91d545a 100644 --- a/docs_en/tutorial/using-docker-compose/index.md +++ b/docs_en/tutorial/using-docker-compose/index.md @@ -247,7 +247,7 @@ volumes: Now that we have our `docker-compose.yml` file, we can start it up! -1. Make sure no other copies of the app/db are running first (`docker ps` and `docker rm -f `). +1. Make sure no other copies of the app/db are running first (`docker-compose down --volumes`). 1. Start up the application stack using the `docker-compose up` command. We'll add the `-d` flag to run everything in the background. @@ -314,4 +314,4 @@ using into the appropriate compose format. At this point, we're starting to wrap up the tutorial. However, there are a few best practices about image building we want to cover, as there is a big issue with the Dockerfile we've been using. So, -let's take a look! \ No newline at end of file +let's take a look!