docker run --rm -v "$(System.DefaultWorkingDirectory):/zap/wrk/:rw" \ zaproxy/zap-stable \

[Ricardo Alfredo Pavez Catrileo]

Dear Sirs:
Good afternoon, I'm trying to send a pipeline from Azure with a YML file to run a full scan test on a demo site, saucedemo.com, but I'm getting the following error. Could you help me determine where the problem might be?

2025-03-28T15:15:50.0294792Z ERROR [Errno 13] Permission denied: '/zap/wrk/zap-fullscan-report.html'
2025-03-28T15:15:50.2063599Z /home/vsts/work/_temp/ff1d2f8f-3bbd-42cf-8b51-9a78fb7fbe13.sh: line 16: -z: command not found
2025-03-28T15:15:50.2075566Z /home/vsts/work/_temp/ff1d2f8f-3bbd-42cf-8b51-9a78fb7fbe13.sh: line 18: -z: command not found
2025-03-28T15:15:50.2083960Z /home/vsts/work/_temp/ff1d2f8f-3bbd-42cf-8b51-9a78fb7fbe13.sh: line 20: -n: command not found
2025-03-28T15:15:50.2099491Z 📄 Checking if the report zap-fullscan-report.html was generated
2025-03-28T15:15:50.2119936Z total 20K
2025-03-28T15:15:50.2122543Z drwxr-xr-x 7 vsts docker 4.0K Mar 28 15:13 .git
2025-03-28T15:15:50.2125310Z -rw-r--r-- 1 vsts docker 985 Mar 28 15:13 README.md
2025-03-28T15:15:50.2127812Z -rw-r--r-- 1 vsts docker 3.0K Mar 28 15:13 azure-pipelines.yml
2025-03-28T15:15:50.2130116Z -rw-r--r-- 1 vsts docker 863 Mar 28 15:13 zap.context
2025-03-28T15:15:50.2130537Z -rw-r--r-- 1 vsts docker 94 Mar 28 15:15 zap.log
2025-03-28T15:15:50.2134422Z ❌ The file zap-fullscan-report.html was not generated.
2025-03-28T15:15:50.2140233Z Complete content of zap.log for debugging:
2025-03-28T15:15:50.2153991Z /home/vsts/work/_temp/ff1d2f8f-3bbd-42cf-8b51-9a78fb7fbe13.sh: line 22: -u: command not found
2025-03-28T15:15:50.2173416Z
2025-03-28T15:15:50.2230360Z ##[error]Bash exited with code '1'.
2025-03-28T15:15:50.2276058Z ##[section]Finishing: Validate login and run ZAP Full Scan

[Simon Bennetts]

Permission denied: '/zap/wrk/zap-fullscan-report.html'

That means ZAP cannot write the specified file.

Docker can be a pain with file permissions - try creating that file before running ZAP and give everyone permissions to write to it.

You will need to create it in $(System.DefaultWorkingDirectory)

Cheers,

Simon