-
Notifications
You must be signed in to change notification settings - Fork 18.8k
Closed
Labels
area/networkingNetworkingNetworking
Description
Description of problem:
The docker network create command does not work with IPv6 subnets using iptables.
docker version
:
Client:
Version: 1.9.1-fc23
API version: 1.21
Package version: docker-1.9.1-2.git78bc3ea.fc23.x86_64
Go version: go1.5.1
Git commit: f7c1d52-dirty
Built: Fri Nov 20 21:07:14 UTC 2015
OS/Arch: linux/amd64
Server:
Version: 1.9.1-fc23
API version: 1.21
Package version: docker-1.9.1-2.git78bc3ea.fc23.x86_64
Go version: go1.5.1
Git commit: f7c1d52-dirty
Built: Fri Nov 20 21:07:14 UTC 2015
OS/Arch: linux/amd64
docker info
:
Server Version: 1.9.1-fc23
Storage Driver: overlay
Backing Filesystem: extfs
Execution Driver: native-0.2
Logging Driver: journald
Kernel Version: 4.2.6-301.fc23.x86_64
Operating System: Fedora 23 (Cloud Edition)
uname -a
:
Linux 4.2.6-301.fc23.x86_64 #1 SMP Fri Nov 20 22:22:41 UTC 2015 x86_64 GNU/Linux
Environment details (AWS, VirtualBox, physical, etc.):
Fedora 23, DigitalOcean
How reproducible:
100%
Steps to Reproduce:
dnf --enablerepo=updates-testing install docker
docker network create --subnet=2001:470::/64 test
Actual Results:
Error response from daemon: unable to add inter-network communication rule: \
iptables failed: iptables --wait -I FORWARD -s 2001:470::1/64 -d 2001:1337::1/64 \
-j DROP: iptables v1.4.21: invalid mask `64' specified
Expected Results:
Docker currently does not deal with IPv6 rules so it could just not do anything in this case either.
Additional info:
On the other hand, IPv6 subnets do work on my workstation that's running with firewalld.
Metadata
Metadata
Assignees
Labels
area/networkingNetworkingNetworking