|author||BIN HU <email@example.com>||2018-10-13 21:18:10 -0700|
|committer||BIN HU <firstname.lastname@example.org>||2018-10-13 21:18:10 -0700|
diff --git a/docs/release/userguide/docker-ipv6-nat.rst b/docs/release/userguide/docker-ipv6-nat.rst
index 314e4ec..eb07eaf 100644
@@ -15,7 +15,7 @@ result, there are still several unresolved issues as to how IPv6 should be used
in a containerized world.
Currently, you can let Docker give each container an IPv6 address from your
-(public) pool, but this has disadvantages (Refer to _):
+(public) pool, but this has disadvantages (Refer to _):
* Giving each container a publicly routable address means all ports (even
unexposed / unpublished ports) are suddenly reachable by everyone, if no
@@ -27,6 +27,7 @@ Currently, you can let Docker give each container an IPv6 address from your
enabled (which, for now, is enabled by default in Docker)
* The userland proxy, however, seems to be on its way out and has various
issues, such as:
* It can use a lot of RAM.
* Source IP addresses are rewritten, making it completely unusable for many
purposes, e.g. mail servers.