From 9aa770679941f40abc13d06831315403fea2a4e2 Mon Sep 17 00:00:00 2001 From: SRINIVASA RAO GURUBELLI Date: Wed, 30 Nov 2016 17:07:25 -0800 Subject: [PATCH] Option --network not valid at least with the latest docker (#755) --network option not valid with docker version 1.11.2. So, proposing to change --network to --net --network=my-bridge-network --- engine/tutorials/networkingcontainers.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/engine/tutorials/networkingcontainers.md b/engine/tutorials/networkingcontainers.md index f05604ebc5..8c552d24c6 100644 --- a/engine/tutorials/networkingcontainers.md +++ b/engine/tutorials/networkingcontainers.md @@ -131,9 +131,9 @@ To build web applications that act in concert but do so securely, create a network. Networks, by definition, provide complete isolation for containers. You can add containers to a network when you first run a container. -Launch a container running a PostgreSQL database and pass it the `--network=my-bridge-network` flag to connect it to your new network: +Launch a container running a PostgreSQL database and pass it the `--net=my-bridge-network` flag to connect it to your new network: - $ docker run -d --network=my-bridge-network --name db training/postgres + $ docker run -d --net=my-bridge-network --name db training/postgres If you inspect your `my-bridge-network` you'll see it has a container attached. You can also inspect your container to see where it is connected: