add to docs that ports do not get exposed when using --net
@@ -237,6 +237,9 @@ with `docker run --net none` which disables all incoming and outgoing
networking. In cases like this, you would perform I/O through files or
`STDIN` and `STDOUT` only.
+Publishing ports and linking to other containers will not work
+when `--net` is anything other than the default (bridge).
+
Your container will use the same DNS servers as the host by default, but
you can override this with `--dns`.
@@ -305,9 +308,8 @@ traffic will be routed though this bridge to the container.
With the networking mode set to `host` a container will share the host's
network stack and all interfaces from the host will be available to the
container. The container's hostname will match the hostname on the host
-system. Publishing ports and linking to other containers will not work
-when sharing the host's network stack. Note that `--add-host` `--hostname`
-`--dns` `--dns-search` and `--mac-address` is invalid in `host` netmode.
+system. Note that `--add-host` `--hostname` `--dns` `--dns-search` and
+`--mac-address` is invalid in `host` netmode.
Compared to the default `bridge` mode, the `host` mode gives *significantly*
better networking performance since it uses the host's native networking stack
