Starting docker.service fails with "iptables: No chain/target/match by that name"

[DavdGao]

trafficstars

• [x] I have tried with the latest version of Docker Desktop
• [x] I have tried disabling enabled experimental features
• [x] I have uploaded Diagnostics
• Diagnostics ID:

Expected behavior

Start docker service normally.

Actual behavior

• Executing sudo service docker start failes with the following error (return by executing sudo dockerd)

INFO[2022-09-07T10:21:38.240467385+08:00] Starting up
INFO[2022-09-07T10:21:38.241381684+08:00] parsed scheme: "unix"                         module=grpc
INFO[2022-09-07T10:21:38.241401549+08:00] scheme "unix" not registered, fallback to default scheme  module=grpc
INFO[2022-09-07T10:21:38.241430023+08:00] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock  <nil> 0 <nil>}] <nil> <nil>}  module=grpc
INFO[2022-09-07T10:21:38.241437644+08:00] ClientConn switching balancer to "pick_first"  module=grpc
INFO[2022-09-07T10:21:38.242270708+08:00] parsed scheme: "unix"                         module=grpc
INFO[2022-09-07T10:21:38.242290236+08:00] scheme "unix" not registered, fallback to default scheme  module=grpc
INFO[2022-09-07T10:21:38.242304982+08:00] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock  <nil> 0 <nil>}] <nil> <nil>}  module=grpc
INFO[2022-09-07T10:21:38.242312359+08:00] ClientConn switching balancer to "pick_first"  module=grpc
INFO[2022-09-07T10:21:38.253567705+08:00] [graphdriver] using prior storage driver: overlay2
INFO[2022-09-07T10:21:38.255652368+08:00] Loading containers: start.
INFO[2022-09-07T10:21:38.291045627+08:00] Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address
INFO[2022-09-07T10:21:38.314005383+08:00] stopping event stream following graceful shutdown  error="<nil>" module=libcontainerd namespace=moby
failed to start daemon: Error initializing network controller: Error creating default "bridge" network: Failed to program FILTER chain: iptables failed: iptables --wait -I FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT: iptables: No chain/target/match by that name.
 (exit status 1)

Information

• Linux distro:

Linux xxxxxxxxxxxxx 4.19.91-009.ali4000.alios7.x86_64 #1 SMP Mon Jan 25 10:47:38 CST 2021 x86_64 x86_64 x86_64 GNU/Linux

• Distro version:
• Docker Desktop Version:

Docker version 19.03.4, build 9013bf583a

• Executing sudo iptables --list returns

Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
DOCKER     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain DOCKER (1 references)
target     prot opt source               destination

Chain DOCKER-ISOLATION-STAGE-1 (0 references)
target     prot opt source               destination
RETURN     all  --  anywhere             anywhere

Chain DOCKER-ISOLATION-STAGE-2 (0 references)
target     prot opt source               destination
RETURN     all  --  anywhere             anywhere

• Executing sudo ip a returns

...
5: docker0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
    link/ether 02:42:66:8f:12:e2 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

[aiordache]

@thaJeztah should we move this to moby/moby?

[docker-robott]

There hasn't been any activity on this issue for a long time. If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment. If not, this issue will be closed in 30 days.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

[docker-robot[bot]]

There hasn't been any activity on this issue for a long time. If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment. If not, this issue will be closed in 30 days.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale