zaproxy: Latest owasp/zap2docker-stable can't find Java 11

Describe the bug

Using the image owasp/zap2docker-stable and running zap-api-scan.py results in the following error:

Exiting: ZAP requires a minimum of Java 11 to run, found

Steps to reproduce the behavior

The full command that we run is:

zap-api-scan.py -I -d -r owasp_report.html -J owasp_report.json -t ${openapi_target} -f openapi -O ${docker_service}:${docker_port} -c api-scan-config.conf

Expected behavior

We would expect the ZAP container to start correctly, but it doesn’t and times out after a while.

Software versions

owasp/zap2docker-stable:latest

Screenshots

No response

Errors from the zap.log file

No response

Additional context

No response

Would you like to help fix this issue?

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 22 (13 by maintainers)

Most upvoted comments

The fix is update Docker to a newer version. adoptium/containers#215 (comment)

The same thing works with tag 2.11.1.

ZAP is using a different/newer base image in 2.12 images (still there’s no issue in ZAP’s images).

Yep, this is the one. Moving to docker-engine 20.10.10+ fixed this for us.

r8ygun on Oct 31, 2022

Thanks for letting us know.

kingthorin on Oct 31, 2022

The fix is update Docker to a newer version. https://github.com/adoptium/containers/issues/215#issuecomment-1142046045

The same thing works with tag 2.11.1.

ZAP is using a different/newer base image in 2.12 images (still there’s no issue in ZAP’s images).

thc202 on Oct 31, 2022

This issue or some of the linked resources may help you: https://github.com/zaproxy/zaproxy/issues/7496

kingthorin on Oct 30, 2022