Verify the requirement for the additional arguments when deploying twistlock defenders.`k3d_command+=" -v /etc/passwd:/etc/passwd@server:*\;agent:* -v /dev/log:/dev/log@server:*\;agent:* -v /run/systemd/private:/run/systemd/private@server:*\;agent:* -v /var/lib/twistlock:/var/lib/twistlock@server:*\;agent:*"` Currently, there's a divergence between CI and local k3d development. If twistlock truly requires the additional arguments, modifications will need to take place in the [k3d cluster creation](https://repo1.dso.mil/big-bang/pipeline-templates/pipeline-templates/-/tree/master/clusters/k3d/dependencies/k3d?ref_type=heads)