From 550c26b9293676f9181ba49b54bd7ba762dd91d2 Mon Sep 17 00:00:00 2001 From: the0ffh Date: Sat, 3 Mar 2018 20:42:53 +0100 Subject: [PATCH] Update networking.md (#7578) Clarified 'pod container' description. --- docs/concepts/cluster-administration/networking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/cluster-administration/networking.md b/docs/concepts/cluster-administration/networking.md index 7f39a3cbfe..7af520617e 100644 --- a/docs/concepts/cluster-administration/networking.md +++ b/docs/concepts/cluster-administration/networking.md @@ -85,7 +85,7 @@ network namespaces - including their IP address. This means that containers within a `Pod` can all reach each other's ports on `localhost`. This does imply that containers within a `Pod` must coordinate port usage, but this is no different than processes in a VM. This is called the "IP-per-pod" model. This -is implemented in Docker as a "pod container" which holds the network namespace +is implemented, using Docker, as a "pod container" which holds the network namespace open while "app containers" (the things the user specified) join that namespace with Docker's `--net=container:` function.