diff options
| author |   BIN HU <bin.hu@att.com> | 2018-10-13 21:18:10 -0700 |
|---|---|---|
| committer | BIN HU <bin.hu@att.com> | 2018-10-13 21:18:10 -0700 |
| commit | 4eb7493ce7b75b49e5f83c8c1d4103458a7cb3c7 (patch) | |
| tree | b12804db9bb075ac8762290d756b12c78589675b /docs | |
| parent | 55527a22b102703d66efda61e44054af26ff16ed (diff) | |
Fix indent issue
Change-Id: If352109fa5092e86ea204346c8ca6efc2ca3e4d0
Signed-off-by: BIN HU <bin.hu@att.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/release/userguide/docker-ipv6-nat.rst | 3 |
1 files changed, 2 insertions, 1 deletions
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. |