mirror of
https://github.com/moby/moby.git
synced 2026-07-04 21:57:53 +00:00
837b3f9576
Before "ip6tables" was enabled by default, dockerd would start normally when: - the kernel had no IPv6 support, or - docker is running as docker-in-docker, and the host doesn't have kernel module 'ip6_tables' loaded. Now, the bridge driver will try to set up its ip6tables chains and it'll fail. By not treating that as an error, the daemon will start and IPv4 will work normally. A subsequent attempt to create an IPv6 network will fail with an error about ip6tables. At that point, the user's options are: - set "ip6tables":false in daemon config - in the DinD case, "modprobe ip6_tables" on the host, or start dockerd on the host with ip6tables enabled (causing the kernel module load). Signed-off-by: Rob Murray <rob.murray@docker.com>