Job report failed to generate report

[Nicollas Teixeira]

Hey guys! Im facing this problem when running automation plan...

If i run it locally with exactly same plan and image it works, if i try to run it on my automated environment on aws im getting this error but its exactly the same of running locally. I tried to check permissions, run as sudo, etc but doesnt work... 

[Nicollas Teixeira]

[Nicollas Teixeira]

evidence from zap.log, only this error related to report, there are other errors but related to report it just say " Job report failed to generate report: /zap/wrk/report.json"

[Simon Bennetts]

How are you starting ZAP?

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

Cheers,

Simon

[Nicollas Teixeira]

Hey Simon!

Im starting using this command: 

docker run --rm --user $(id -u):$(id -g) -v $(pwd):/zap/wrk/:rw -t softwaresecurityproject/zap-stable bash -c "zap.sh -cmd -addonupdate; zap.sh -cmd -autorun /zap/wrk/exported.yaml"

Hmm, I don't think the problem is that I can't access the file, it's not generating the file, I'm having a failure in the report generation job.

[Simon Bennetts]

Why are you specifying "--user $(id -u):$(id -g)" ?

What happens if you dont include that part?

I suspect that the user you are using in docker does not have write access to /zap/wrk

You can test that using a command like:

• docker run -v $(pwd):/zap/wrk/:rw -t ghcr.io/zaproxy/zaproxy:stable touch /zap/wrk/test.txt

as per the last link I shared.

Cheers,

Simon

[Nicollas Teixeira]

Oh okay, i will try this command and i already tested without  "--user $(id -u):$(id -g)" and still the same.

[Simon Bennetts]

What happens when you try the command:

• docker run -v $(pwd):/zap/wrk/:rw -t softwaresecurityproject/zap-stable touch /zap/wrk/test.txt

Is there a text.txt file once docker has existed?

[Nicollas Teixeira]

Hmm, its weird but probably permission issue...

[Simon Bennetts]

Yep, thats what I expected.

Have a look at your filestore perms.

You can also try creating the expected files in advance (eg test1.txt for the testing).

[Nicollas Teixeira]

yeah, it was permission problem, Now that I fixed this folder permission issue, it is having problem launching the browser... im using the docker command to update the add-ons btw

[Nicollas Teixeira]

this error also

[Simon Bennetts]

There was a problem with the last Network add-on release.

Try again making sure that all of your add-ons are up to date - the latest Network add-on should have fixed the problem we became aware of.

Cheers,

Simon