From 74380b3890759c82ec2e838b74f8e46cab6338dc Mon Sep 17 00:00:00 2001 From: BIN HU Date: Sat, 13 Oct 2018 21:18:10 -0700 Subject: Fix indent issue Change-Id: If352109fa5092e86ea204346c8ca6efc2ca3e4d0 Signed-off-by: BIN HU (cherry picked from commit 4eb7493ce7b75b49e5f83c8c1d4103458a7cb3c7) --- docs/release/userguide/docker-ipv6-nat.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/release/userguide/docker-ipv6-nat.rst b/docs/release/userguide/docker-ipv6-nat.rst index 314e4ec..eb07eaf 100644 --- a/docs/release/userguide/docker-ipv6-nat.rst +++ b/docs/release/userguide/docker-ipv6-nat.rst @@ -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 [1]_): +(public) pool, but this has disadvantages (Refer to [1]_): * 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. -- cgit 1.2.3-korg