twistlock.sh onebox failure

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

twistlock.sh onebox failure

L1 Bithead

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? 

1 REPLY 1

L1 Bithead

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.

  • 1917 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!