ZAP refuses to start
Summary
We were running the publicly available OWASP ZAP container and triggering the scans by issuing :zap-cli" commands within the container image. However we were asked by our IA team to transition using the OWASP ZAP image container from IronBank instead. Try following the instructions to run the container and am having trouble getting it working. Also "zap-cli" does not appear to exist inside the container either.
Steps to reproduce
sudo docker run -d -p 8080:8080 -e ZAP_API_KEY=$ZAP_API_KEY registry1.dsop.io/ironbank/opensource/owasp-zap/owasp-zap -config api.addrs.addr.name=.* -config api.addrs.addr.regex=true -config api.key=$ZAP_API_KEY
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
bb9accad7e74 registry1.dsop.io/ironbank/opensource/owasp-zap/owasp-zap "/zap/entrypoint.s..." About a minute ago Up About a minute (unhealthy) 0.0.0.0:8080->8080/tcp peaceful_heyrovsky
What is the current bug behavior?
Container does not enter healthy state.
What is the expected correct behavior?
Container enters healthy state.
Relevant logs and/or screenshots
See above.
Possible fixes
This may be related to the missing zap-cli command.
Defintion of Done
-
Bug has been identified and corrected within the container