Running ZAP in docker.

[Cristhian A. Ferreira Suazo]

Hello guys, I'm trying to run ZAP headless in a docker container using the following commands:

docker pull softwaresecurityproject/zap-stable

sudo docker run -p 5000:5000 -i softwaresecurityproject/zap-stable zap.sh -daemon -port 5000 -host 0.0.0.0

But It returns the error bellow:

5033 [ZAP-daemon] INFO  org.parosproxy.paros.CommandLine - Add-on downloaded to: /home/zap/.ZAP/plugin/selenium-release-15.14.0.zap
35047 [ZAP-daemon] WARN  org.zaproxy.addon.network.ExtensionNetwork - Failed to start the main proxy: java.net.BindException Address already in use
35047 [ZAP-daemon] ERROR org.parosproxy.paros.CommandLine - Terminating ZAP, unable to start the main proxy.
39677 [ZAP-daemon] INFO  org.zaproxy.zap.DaemonBootstrap - OWASP ZAP 2.13.0 terminated.

I tried using other ports and using different commands but it results to the same error. What should I do?

[Apollos]

Experiencing a similar error, and I believe this post is referencing it as well: https://groups.google.com/g/zaproxy-users/c/AsgNc3FuADA/m/bglAg3M6AAAJ

I pull from softwaresecurityproject/zap-stable as well and attempted changing ports to no avail.

Tests were running as expected roughly 24h ago. Last, I noticed that removing the `-addoninstallall` addresses the issue at the expense of add-ons, however, leading me to assume there may be a rogue alpha/beta (hopefully not stable) add-on update pushed recently.

[Simon Bennetts]

We are aware of a problem with the network add-on.

A fix should be available soon - we'll post here when it is available.

Thank you for your patience,

Simon

[Simon Bennetts]

This issue is fixed with the latest version of Network add-on.

Thanks for reporting this,

Simon