twistlock.sh onebox failure

MarkSteven — Wed, 13 Jul 2022 14:53:47 GMT

The following warnings are reported when executing "twistlock.sh -s onebox"

WARNING: You're not using the default seccomp profile
WARNING: IPv4 forwarding is disabled
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Initializing Twistlock environment.
Installing Twistlock Console (localhost).
WARNING: You're not using the default seccomp profile
WARNING: IPv4 forwarding is disabled
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

followed by this error:

/usr/bin/docker-current: Error response from daemon: driver failed programming external connectivity on endpoint twistlock_console (9f248c72a3e054f6991713497b7e0cd345a0d20047f4480bc8cdf9412629ed01): (iptables failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 8094 -j DNAT --to-destination 172.17.0.3:8094 ! -i docker0: iptables: No chain/target/match by that name.
(exit status 1))..
Failed to run Twistlock Console.

Is the failure due to the reported warnings?

Re: twistlock.sh onebox failure

MarkSteven — Wed, 13 Jul 2022 19:07:18 GMT

Never mind. I found the issue. Restarting docker re-added the missing iptable rules. Apparently the firewall had been restarted which removed the docker rules.

topic twistlock.sh onebox failure in General Topics

twistlock.sh onebox failure

Re: twistlock.sh onebox failure