Fixes #11630
Signed-off-by: Ankush Agarwal <ankushagarwal11@gmail.com>
| ... | ... |
@@ -279,6 +279,13 @@ container. The container's hostname will match the hostname on the host |
| 279 | 279 |
system. Publishing ports and linking to other containers will not work |
| 280 | 280 |
when sharing the host's network stack. |
| 281 | 281 |
|
| 282 |
+Compared to the default `bridge` mode, the `host` mode gives *significantly* |
|
| 283 |
+better networking performance since it uses the host's native networking stack |
|
| 284 |
+wheras the bridge has to go through one level of virtualizaion through the |
|
| 285 |
+docker daemon. It is recommended to run containers in this mode when their |
|
| 286 |
+networking performance is critical, for example, a production Load Balancer |
|
| 287 |
+or a High Performance Web Server. |
|
| 288 |
+ |
|
| 282 | 289 |
> **Note**: `--net="host"` gives the container full access to local system |
| 283 | 290 |
> services such as D-bus and is therefore considered insecure. |
| 284 | 291 |
|