Trying to run zap docker container on azure app service

[Patrick Dwyer]

I'm trying to get the docker container "owasp/zap2docker-stable:latest" running on an Azure App Service for Containers.

This is in my startup script...

zap-x.sh -daemon -port 8080 -host 0.0.0.0 -config api.addrs.addr.name=.* -config api.addrs.addr.regex=true -config api.key=$API_KEY

If I try browsing to the app service it just keeps redirecting to itself.

There are a couple of factors that might be contributing to this. TLS termination is handled by the app service platform. And I don't think there is a way for ZAP to figure out the public hostname.

I've tried adding an entry to /etc/hosts that corresponds to the public hostname and internal network interface IP address. And then using the hostname for the host parameter but that hasn't worked for me so far.

Any help would be much appreciated. Apologies if I haven't included enough information up front.

[Patrick Dwyer]

Never mind, I have a simpler approach for our use case.

[hauschu...@gmail.com]

If you think it might be something that others might run into, please feel free to post a description here!

[Patrick Dwyer]

Yeah, good point. I've posted here https://groups.google.com/forum/#!topic/zaproxy-users/gyyfxG-jow4 but others might end up on this post.

I've completely changed tack. Instead of running the container as a web app and having it run all the time I'm just running it as part of our release process.

https://github.com/patros/docker-zap-scanner