iptables: No chain/target/match error (with docker network create)

docker networking iptables
Christian68 picture Christian68 · Dec 13, 2018 · Viewed 7.5k times · Source

When creating a network (docker network create -d bridge my-nw), I obtained this error in response:

Error response from daemon: Failed to Setup IP tables: Unable to enable SKIP DNAT rule: (iptables failed: iptables --wait -t nat -I DOCKER -i br-bedba04c7349 -j RETURN: iptables: No chain/target/match by that name.

What do I need to do to go around? Docker or IP Table modifications?

Answer

BMitch picture BMitch · Dec 13, 2018

Something has deleted the docker iptables entries. Docker will recreate them if you restart it (systemctl restart docker). You'll want to disable anything else that manages iptables to prevent this from happening in the future.

Related questions

Docker container can not ping the outside world - iptables

exploring Docker 17.06. I've installed docker on Centos 7 and created a container. Started the container with the default bridge. I can ping both host adapters, but not the outside world e.g. www.google.com All advise out there is based …

Read More
Network unreachable inside docker container without --net=host parameter

Problem: there is no internet connection in the docker container. Symptoms: ping 8.8.8.8 doesn't work. Wireshark from host system gives back: 19 10.866212113 172.17.0.2 -> 8.8.8.8 ICMP 98 Echo (ping) request id=0x0009, seq=0/0, ttl=64 20 11.867231972 172.17.0.2 -> 8.8.8.8 ICMP 98 Echo (ping) request id=0x0009, seq=1/256, ttl=64 21 12.868331353 172.17.0.2 …

Read More
Does Docker automate IP masquerade rules in iptables for bridge networks?

I have docker-1.9.1 running on a QNAP raid machine. It has the default bridge network using subnet 10.0.3.0/24. In iptables I see a rule in the nat table: -A POSTROUTING -s 10.0.3.0/24 ! -d 10.0.3.0/24 -j MASQUERADE I am assuming that Docker created this …

Read More