Skip to content

Added statement clarifying support for Transparent network mode with IPv6 #1996

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -58,7 +58,10 @@ The Host Networking Service (HNS) and the Host Compute Service (HCS) work togeth

The following networking options are currently **NOT** supported on Windows:

- From Windows Server 2022 onwards, Windows containers attached to l2bridge networks support the IPv6 stack. However, Windows containers attached to NAT and overlay networks do not support communicating over the IPv6 stack.
- From Windows Server 2022 onwards, Windows containers have the following support for IPv6 networking:
- Containers attached to l2bridge networks support the IPv6 stack.
- Containers attached to transparent networks support communication using IPv6 with self assigned IP addresses, but do not have support for HNS provided IP address assignment and other network services such as Load Balancing and ACLs.
- Windows containers attached to NAT and overlay networks do not support communicating over the IPv6 stack.
- Encrypted container communication via IPsec.
- [Host mode](https://docs.docker.com/ee/ucp/interlock/config/host-mode-networking/) networking.
- Networking on virtualized Azure infrastructure via the transparent network driver.