ARM/M1 support for docker image

Using the existing image doesn’t work, even emulated, on M1 Mac; the webswing page hangs mid load.

I might recommend the following changes to the dockerfile to get native ARM/M1 support:

1. Update the base image for the builder to use am ARM JDK, like bellsoft/liberica-openjdk-alpine:11
2. Remove JAVA_HOME bits because a) They are platform-specific which causes rebuilding on ARM to pull the ARM ubuntu image then reference the x86 JRE b) They don’t seem to be required; I removed them and the app works fine

Finagling the image a bit more to pull files from git into the builder then copy from builder into the image, I was able to get zap running pretty well on my M1 mac mini. For an official build, pulling from git wouldn’t be relevant.

[anarang]

@psiinon thanks, it worked! sorry I missed it in the docs.

[psiinon]

On https://www.zaproxy.org/docs/docker/baseline-scan/

To run it with no ‘file’ params use:

docker run -t owasp/zap2docker-stable zap-baseline.py -t https://www.example.com

If you use ‘file’ params then you need to mount the directory those file are in or will be generated in, eg

docker run -v $(pwd):/zap/wrk/:rw -t owasp/zap2docker-stable zap-baseline.py \
    -t https://www.example.com -g gen.conf -r testreport.html

Also in https://www.zaproxy.org/docs/docker/diagnosing-problems/#cannot-access-created-files