I like to run a container in the "bridge" network while listening to IPv6 traffic. I found this answer, so I tried the following, but it does not work:

 

It works only if I use the "host" network or if I set a fixed IPv6 through the "br0" network.

 

I even tried the example in the comments, but it doesn't work, too:

 

IPv6 works on the host as expected:

 

 

 

Ok, IPv6 is disabled for the "bridge" network:

 

docker network inspect bridge[
    {
        "Name": "bridge",
        "Id": "0621a44885d45ecf2d614375b8b77f4a2b2197d16aa6d0332207efb758ca44d4",
        "Created": "2021-07-01T23:15:29.325813611+02:00",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.17.0.0/16",
                    "Gateway": "172.17.0.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {},
        "Options": {
            "com.docker.network.bridge.default_bridge": "true",
            "com.docker.network.bridge.enable_icc": "true",
            "com.docker.network.bridge.enable_ip_masquerade": "true",
            "com.docker.network.bridge.host_binding_ipv4": "0.0.0.0",
            "com.docker.network.bridge.name": "docker0",
            "com.docker.network.driver.mtu": "1500"
        },
        "Labels": {}
    }
]

 

 

After creating /etc/docker/daemon.json with the following content:

{
  "ipv6": true,
  "fixed-cidr-v6": "2002:ac11:0000::/48"
}

 

And restarting docker, the "bridge" network supports ipv6:

docker network inspect bridge
[
    {
        "Name": "bridge",
        "Id": "7808c2176e7ad3d54867e8b96f90f4fd86597079f7abd0290fdc272746c66130",
        "Created": "2021-07-02T08:24:29.197496024+02:00",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": true,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.17.0.0/16",
                    "Gateway": "172.17.0.1"
                },
                {
                    "Subnet": "2002:ac11::/48"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "5b183a12fd4b6209084439415c163fbc33511922876c0ae124a715c8e27ccf5d": {
                "Name": "npm",
                "EndpointID": "602b22bf2741cbfc00e1356975034947bfae33dafab5a17021bae37b150ca155",
                "MacAddress": "02:42:ac:11:00:02",
                "IPv4Address": "172.17.0.2/16",
                "IPv6Address": "2002:ac11::242:ac11:2/48"
            }
        },
        "Options": {
            "com.docker.network.bridge.default_bridge": "true",
            "com.docker.network.bridge.enable_icc": "true",
            "com.docker.network.bridge.enable_ip_masquerade": "true",
            "com.docker.network.bridge.host_binding_ipv4": "0.0.0.0",
            "com.docker.network.bridge.name": "docker0",
            "com.docker.network.driver.mtu": "1500"
        },
        "Labels": {}
    }
]

 

But there is still something wrong as my npm container is able to connect IPv6 addresses, but it seems, it is not able to resolve IPv6 domains:

 

EDIT: Ok, this is strange. Although I disabled IPv6 for the bridge network, the NPM container is still able to connect through IPv6?!

 

 

 

14 minutes ago, mgutt said:

Ok, IPv6 is disabled for the "bridge" network:

 

It is disabled because it interferes with the IPv6 networking of Unraid itself.

 

If you want to use IPv6, it is available for custom networks.

 

How do I enable ipv6 for a custom docker bridge network that I have already created ?