ZAP 2.17 fails to start/connect in Docker container (works fine with 2.14)

[Анна Б]

Hi Team,

We are facing an issue with ZAP 2.17 in our Docker environment. The same setup works perfectly with ZAP 2.14. The script (zap-full-scan.py) cannot connect to ZAP after the 600-second timeout period.

Environment:

• • Working Version: 2.14 (ghcr.io/zaproxy/zaproxy:20240103-stable)

  • Failing Version: 2.17 (latest zaproxy/zap-stable)

  • Docker host: Linux

  • Java Version: 17.0.18
    
    Error Log:
    The ZAP process starts (we can see the initialization logs), but the Python script fails to connect. Here is the relevant part of the log:
    
    2026-02-16 14:10:17,959 Starting new HTTP connection (1): localhost:47141
    2026-02-16 14:10:18,960 I/O error: [Errno 5] Failed to connect to ZAP after 600 seconds
    Traceback (most recent call last):
      File "/zap/zap-baseline.py", line 343, in main
        wait_for_zap_start(zap, timeout * 60)
      File "/zap/zap_common.py", line 331, in wait_for_zap_start
        raise IOError(
    OSError: [Errno 5] Failed to connect to ZAP after 600 seconds
    Found Java version 17.0.18
    Available memory: 128777 MB
    Using JVM args: -Xmx32194m
    554 [main] INFO  org.parosproxy.paros.Constant - Copying default configuration to /home/zap/.ZAP/config.xml
    688 [main] INFO  org.parosproxy.paros.Constant - Creating directory /home/zap/.ZAP/session
    688 [main] INFO  org.parosproxy.paros.Constant - Creating directory /home/zap/.ZAP/dirbuster
    689 [main] INFO  org.parosproxy.paros.Constant - Creating directory /home/zap/.ZAP/fuzzers

• 1. ZAP process starts (we can see the initialization logs)

  2. The script tries to connect to port

  3. Connection fails after 10 minutes (600 seconds)

  4. Same Dockerfile and scripts work flawlessly with ZAP 2.14

  Full logs and artifacts:

  • Full log.out (attached)

  • Dockerfile (attached)
    
    Run Command (example):  docker run --rm -v $(pwd):/zap/wrk/:rw -t zap zap-full-scan.py -t http://localhost:3000/ -r testreport.html --hook=/zap/auth_hook.py -z "auth.loginurl=http://localhost:3000/#/login auth.username=*** auth.password=***"
    
    Any guidance on what might be causing this regression would be greatly appreciated.
    
    Are there new requirements or configuration parameters needed for ZAP 2.17 to work properly in Docker environments?

    Thanks,
    Anna

  
  
  

[psiinon]

I can see this error in the zap.log file:

11268 [ZAP-daemon] INFO  org.parosproxy.paros.extension.ExtensionLoader - Initializing ExtensionFoxhound - Foxhound ZAP AddOn
11271 [ZAP-daemon] INFO  org.zaproxy.zap.extension.foxhound.config.FoxhoundConstants - Loading source and sink config from /org/zaproxy/zap/extension/foxhound/resources/sourcessinks.json
11287 [ZAP-daemon] WARN  org.zaproxy.zap.extension.foxhound.FoxhoundExportServer - An error occurred while starting the proxy.
java.net.BindException: Address already in use

The Foxhound add-on is alpha and not included in the stable release, you are adding it via the following command in your docker file:

RUN ./zap.sh -cmd -silent -addoninstallall

We do not recommend installing all of the add-ons in production as some of them are at a very early stage and can cause problems.

Try running without this add-on.

Cheers,

Simon

--
ZAP by Checkmarx: https://www.zaproxy.org/
---
You received this message because you are subscribed to the Google Groups "ZAP User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zaproxy-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/zaproxy-users/f7cf7e67-c132-40ce-b9f7-7199d6828cefn%40googlegroups.com.

--

ZAP Project leader