ubuntu-docker-images team mailing list archive

[Sergio Durigan Junior <sergio.durigan@xxxxxxxxxxxxx>]

Hi guys,

I found that if you explicitly specify the subnet when creating the
network, like this:

  $ docker network create --ipv6 --subnet "2001:db8:1::/64" networkname

This assumes that daemon.json is configured like this:

{
	"ipv6": true,
	"fixed-cidr-v6": "2001:db8::/64"
}


The problem, of course, is that we don't know what the fixed-cidr-v6
will be on anyone's machine.  We could parse it, but that's really not
ideal.

While at it, I have also verified that removing all the "docker network"
bits from the test file does solve the issue, as expected.  So maybe
that's the best approach right now (until we have a better way to tackle
the IPv6 network creation problem).

WDYT?

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14