kotovalexarian-likes-github/moby--moby
1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
Code Releases Activity

Don't make the user get a container alreayd exists error

Browse source 
Docker-DCO-1.1-Signed-off-by: SvenDowideit <SvenDowideit@home.org.au> (github: SvenDowideit)
This commit is contained in:
SvenDowideit 2014-07-07 10:28:53 +10:00
parent 42a28f79dc
commit 6a9c6d3bf1
1 changed files with 7 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
docs/sources/userguide/dockerlinks.md
View file

@ -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