ZAP on Docker fails because check for updates fails (behind corporate proxy)

[Zaphod]

I'm new to ZAP and trying to get started with the Docker version. I am running it in a Kali VM and the system I am running the VM on is behind a corporate firewall. It is failing to start because it can't reach GitHub to check for updates (least think so).

Is there a way to disable this check? I would rather not setup a way to get through the proxy since the end goal is to run this locally as part of an automated scanning process so disabling the check is best. I checked the help file and did some searching but didn't see a way to disable the check.

Here is the error: 

54133 [ZAP-cfu] WARN  org.zaproxy.zap.extension.autoupdate.ExtensionAutoUpdate - Failed to check for updates using: https://raw.githubusercontent.com/zaproxy/zap-admin/master/ZapVersions-2.10.xml

java.net.UnknownHostException: raw.githubusercontent.com

        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:220) ~[?:?]

<snipped>

54799 [ZAP-daemon] ERROR org.parosproxy.paros.CommandLine - Check for updates call failed

 Here is the command I am running

docker run -t owasp/zap2docker-stable zap-baseline.py -t http://localhost:3000

Thanks for the help

[Simon Bennetts]

The baseline scan should carry on regardless so you shouldnt actually have to make any changes.

But passing the "-silent" flag though to ZAP should also turn it off: -z "-silent"