From 6a9c6d3bf12982ca31e0b38cd323073b44c98456 Mon Sep 17 00:00:00 2001 From: SvenDowideit Date: Mon, 7 Jul 2014 10:28:53 +1000 Subject: [PATCH] Don't make the user get a container alreayd exists error Docker-DCO-1.1-Signed-off-by: SvenDowideit (github: SvenDowideit) --- docs/sources/userguide/dockerlinks.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/sources/userguide/dockerlinks.md b/docs/sources/userguide/dockerlinks.md index 91c6cb355b..bfbcdb3bd6 100644 --- a/docs/sources/userguide/dockerlinks.md +++ b/docs/sources/userguide/dockerlinks.md @@ -116,8 +116,8 @@ We can also use `docker inspect` to return the container's name. > **Note:** > Container names have to be unique. That means you can only call -> one container `web`. If you want to re-use a container name you must delete the -> old container with the `docker rm` command before you can create a new +> one container `web`. If you want to re-use a container name you must delete +> the old container with the `docker rm` command before you can create a new > container with the same name. As an alternative you can use the `--rm` > flag with the `docker run` command. This will delete the container > immediately after it stops. @@ -133,6 +133,11 @@ container, this one a database. Here we've created a new container called `db` using the `training/postgres` image, which contains a PostgreSQL database. +We need to delete the `web` container we created previously so we can replace it +with a linked one: + + $ docker rm -f web + Now let's create a new `web` container and link it with our `db` container. $ sudo docker run -d -P --name web --link db:db training/webapp python app.py