zap-full-scan Report File is not written after full scan completes. No errors reported in the console. baseline scan works fine.

[chaoscode]

Describe the bug

When running the report file is not written

Steps to reproduce the behavior

1: install docker desktop
2: run docker (docker run -v C:\user{username}\Desktop\Work:/zap/wrk/:rw -t ghcr.io/zaproxy/zaproxy:stable zap-full-scan.py -t https://www.{domain}.com/ -j {domain}_Full_report.json -g gen.conf -quickprogress -v)
3: observe no report file is written to the mounted path

Expected behavior

the file is written or the console outputs an error message explaining what happened

Software versions

I have tried docker desktop and TrueNAS Scale with this and the latest tag. I have the same issue. The file will not write to a mount.
I am using quite a few other scanners that all mount to this folder, and they are able to write the report files just fine.

Screenshots

Errors from the zap.log file

no log file exists in the home directory.

Additional context

I have used the touch command per the documentation to confirm that files are touched, and no errors are output by the console.

I have no issues with running the baseline scan and getting the report to write from the same docker.

Would you like to help fix this issue?

• Yes

[kingthorin]

Exclude the -g, you shouldn't be generating the config on every run:
https://www.zaproxy.org/docs/docker/full-scan/#usage

Also quickprogress because you aren't using quickscan you're using a packaged scan.

[thc202]

Just to confirm it's a typo, did you mean to use -J (instead of -j)?

[thc202]

In any case we should definitely error on invalid command line args.

[kingthorin]

no log file exists in the home directory.

Nor should it. (ZAP home, not user home.)
https://www.zaproxy.org/faq/how-do-you-configure-zap-logging/

ZAP logs to a file called “zap.log” in the ZAP ‘home’ directory.