Docker logs come back in bulk instead of live progress output
Author: jakubtrebacz-devCreated Dec 19, 2024Updated Sep 28, 2026
Labelsbug
Describe the bug:
When running zap-baseline.py on docker image ghcr.io/zaproxy/zaproxy:stable it looks like the python script is frozen for the duration of execution, then suddenly comes back with all the output in one go.
This makes long running scans particularly frustrating
Steps to reproduce the behavior:
- docker pull ghcr.io/zaproxy/zaproxy:stable
- $container_id = docker run -d -u 0 -v "$zapPath/:/zap/wrk/" -p 8080:8080 "$zapImage" "$zapRunScript" -t "$TargetUrl" -J "$ZapReportFile.json" -r "$ZapReportFile.html"
- docker logs -f $container_id
To confirm behaviour run the container, connect to it, and run the zap-baseline.py with same inputs, it will freeze up and eventually return std console output in one go which suggests something wrong with .py script or your image rather than docker logs command.
Expected behavior:
Live std output as the tests run
Software versions:
v2.15.0
Screenshots:
N/A
Errors from the zap.log file:
N/A
Additional context:
No response
Would you like to help fix this issue?
- Yes
Source: zaproxy/zaproxy