From 5ce24b0587be6a4465b64e0d3c6d59ec0b59237c Mon Sep 17 00:00:00 2001 From: Alan Thompson Date: Thu, 9 Mar 2017 19:10:04 -0600 Subject: [PATCH] Update work-with-networks.md (#2236) Clarify what is being connected to the network. --- engine/userguide/networking/work-with-networks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/engine/userguide/networking/work-with-networks.md b/engine/userguide/networking/work-with-networks.md index 6f273a1e09..3e29003f61 100644 --- a/engine/userguide/networking/work-with-networks.md +++ b/engine/userguide/networking/work-with-networks.md @@ -685,7 +685,7 @@ containers use, it does have some limitations. Environment variable injection is static in nature and environment variables cannot be changed after a container is started. The legacy `--link` flag shares all environment variables to the linked container, but the `docker network` command -has no equivalent. When you connect to a network using `docker network`, no +has no equivalent. When you connect a container to a network using `docker network`, no environment variables can be dynamically shared among containers. #### Understanding network-scoped aliases