- describe Docker's custom chains
- describe the new direct routing options
- use documentation address ranges in examples
Signed-off-by: Rob Murray <rob.murray@docker.com>
Also, daemon.json "ipv6":true only enables IPv6 for the default bridge,
it's not required for a user-defined bridge.
Signed-off-by: Rob Murray <rob.murray@docker.com>
Google's DNS servers are currently used by containers on the default
bridge network, when none of the host's /etc/resolv.conf nameservers
are usable (host loopback addresses that the container can't see).
But, if a server is supplied via the --dns option, it'll just appear
in the container's resolv.conf (on the default bridge) or as an
upstream server for the internal resolver.
So, fix the networking-intro page's description, noting that requests
to --dns servers happen in the container's namespace.
Signed-off-by: Rob Murray <rob.murray@docker.com>
Since 26.0.0, IPv6 nameservers in the host's /etc/resolv.conf file
have been treated the same as IPv4 nameservers - the internal DNS
server will use them as upstream servers, they won't be left in the
container's resolv.conf. (So, there's no longer any race between
the internal server and IPv6 upstream servers when using musl-libc.)
Signed-off-by: Rob Murray <rob.murray@docker.com>
Headings should be surrounded by blank lines
Rationale: Aside from aesthetic reasons, some parsers, including kramdown, will not parse headings that don't have a blank line before, and will parse them as regular text.
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Corrects a false statement that you can't connect to multiple networks
with the `--network` flag.
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
This tutorial was duplicated from the bridge page and didn't cover the
overlay driver, probably a copy/paste issue.
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
* tier 1 updates
* update overview and refresh quickstart steps
* update description and refresh for accuracy
* fix capitalization
* optimize image and replace low res image with console example
This change adds more introductory information about container
networking to the networking overview page, moving it from the docker
run reference page.
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
