diff --git a/_data/toc.yaml b/_data/toc.yaml index 49cadfa8f5..75b68785b2 100644 --- a/_data/toc.yaml +++ b/_data/toc.yaml @@ -1353,7 +1353,7 @@ manuals: - sectiontitle: Network drivers section: - path: /network/drivers/ - title: Drivers overview + title: Overview - path: /network/drivers/bridge/ title: Bridge - path: /network/drivers/overlay/ @@ -1365,7 +1365,7 @@ manuals: - path: /network/drivers/macvlan/ title: Macvlan - path: /network/drivers/none/ - title: None + title: None (no networking) - path: /network/proxy/ title: Configure Docker to use a proxy server - path: /config/daemon/ipv6/ diff --git a/engine/install/debian.md b/engine/install/debian.md index 6a33b44de9..17bb851679 100644 --- a/engine/install/debian.md +++ b/engine/install/debian.md @@ -19,11 +19,10 @@ To get started with Docker Engine on Debian, make sure you > **Note** > -> If you use ufw to manage firewall settings, note that when you expose -> container ports using Docker, those ports bypass any firewall rules that -> you configure with ufw. See -> [Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw) -> for details. +> If you use ufw to manage firewall settings, it's important to be aware that +> when you expose container ports using Docker, these ports bypass any +> firewall rules set up with ufw. For more information, refer to +> [Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw). ### OS requirements diff --git a/engine/install/raspbian.md b/engine/install/raspbian.md index b11bf9e539..176d528979 100644 --- a/engine/install/raspbian.md +++ b/engine/install/raspbian.md @@ -16,11 +16,10 @@ To get started with Docker Engine on Raspbian, make sure you > **Note** > -> If you use ufw to manage firewall settings, note that when you expose -> container ports using Docker, those ports bypass any firewall rules that -> you configure with ufw. See -> [Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw) -> for details. +> If you use ufw to manage firewall settings, it's important to be aware that +> when you expose container ports using Docker, these ports bypass any +> firewall rules set up with ufw. For more information, refer to +> [Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw). ### OS requirements diff --git a/engine/install/ubuntu.md b/engine/install/ubuntu.md index 36e1035edc..be55182a5b 100644 --- a/engine/install/ubuntu.md +++ b/engine/install/ubuntu.md @@ -24,11 +24,10 @@ To get started with Docker Engine on Ubuntu, make sure you > **Note** > -> If you use ufw to manage firewall settings, note that when you expose -> container ports using Docker, those ports bypass any firewall rules that -> you configure with ufw. See -> [Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw) -> for details. +> If you use ufw to manage firewall settings, it's important to be aware that +> when you expose container ports using Docker, these ports bypass any +> firewall rules set up with ufw. For more information, refer to +> [Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw). ### OS requirements diff --git a/network/drivers/bridge.md b/network/drivers/bridge.md index a249bf9a13..5b560ec57e 100644 --- a/network/drivers/bridge.md +++ b/network/drivers/bridge.md @@ -128,8 +128,8 @@ daemon. The following tables shows which options have equivalent flags in the | `com.docker.network.driver.mtu` | `--mtu` | | `com.docker.network.container_iface_prefix` | - | -The Docker daemon supports a `--bridge` flag, which you can use to define a -custom network bridge. You use this option if you want to run multiple daemon +The Docker daemon supports a `--bridge` flag, which you can use to define +your own `docker0` bridge. Use this option if you want to run multiple daemon instances on the same host. For details, see [Run multiple daemons](../../engine/reference/commandline/dockerd.md#run-multiple-daemons). diff --git a/network/drivers/index.md b/network/drivers/index.md index 0b087c2363..8fd16163da 100644 --- a/network/drivers/index.md +++ b/network/drivers/index.md @@ -42,12 +42,12 @@ exist by default, and provide core networking functionality: ### Network driver summary -- The default bridge network is commonly used for running containers that don't - require custom networking configurations, such as container-to-container - connectivity. -- User-defined bridge networks enable on the same Docker host to communicate - with each other. A user-defined network typically defines an isolated network - for multiple containers belonging to a common project or component. +- The default bridge network is good for running containers that don't require + special networking capabilities. +- User-defined bridge networks enable containers on the same Docker host to + communicate with each other. A user-defined network typically defines an + isolated network for multiple containers belonging to a common project or + component. - Host network shares the host's network with the container. When you use this driver, the container's network isn't isolated from the host. - Overlay networks are best when you need containers running on different diff --git a/network/index.md b/network/index.md index 2be7cc35aa..6557e85f69 100644 --- a/network/index.md +++ b/network/index.md @@ -23,7 +23,7 @@ a gateway, a routing table, DNS services, and other networking details. That is, unless the container uses the `none` network driver. This page describes networking from the point of view of the container. -This page describes the concepts around container networking. +This page also describes the concepts around container networking. This page doesn't describe OS-specific details about how Docker networks work. For information about how Docker manipulates `iptables` rules on Linux, see [Packet filtering and firewalls](packet-filtering-firewalls.md). @@ -116,7 +116,7 @@ of different factors: Under most circumstances, name resolution with multiple nameservers should work as follows: -1. The container emits requests to **all** nameservers that you specify. +1. The container emits requests to all nameservers that you specify. 2. The container uses the first response returned by any of the nameservers. Even if the first response is `NXDOMAIN`, or similar.