Open akerouanton opened 1 month ago
@akarshm can you take a look at this feature request?
@grcusanz @adrianm-msft could networking take a look at these asks? We can discuss it in the next Triage call.
@akerouanton, which version of Windows was this tested on?
I'm using Windows 11 Pro and the build number is 22631.3880.
Hi, we'll be able to provide updates for your requests in a few days, once we've met with the product team.
Hi,
moby / libnetwork maintainer here.
As the OMB memorandum M-21-07 will come into force in Sep. 2025, we started working on IPv6 improvements for Linux containers and we’ll need to add IPv6 support to Windows containers before that deadline. Since the API documentation for HNS doesn’t mention IPv6 limitations, I started playing with the API to see what roadblockers I could find.
I’m opening this ticket to document what I found and make feature requests. All the
docker
commands below are run against this branch: https://github.com/moby/moby/pull/48285.So far, I only tested the
nat
driver, but we’ll need similar improvements for other drivers.Here’s a TL;DR list of Feature Requests:
Create an IPv6 network
So far, I’m able to create a network with static IPv6 subnet, but unlike IPv4, HNS won’t dynamically allocate IPv6 subnets:
Run a container attached to an IPv6 network
Container's IP address isn't automatically added to its interface:
Ping the host from the container (and vice-versa)
Pinging the host from the container doesn't work (although the reverse does). It seems there's a missing firewall policy to allow outbound connectivity:
And taking a look with
pktmon
: