-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Report: failed to read from json (Docker) #294
Comments
@xpfgsyb Thanks. I will check the issue. |
I've seen the same issue but on a normal ubuntu server. I run the report command via a bash script. It works when I run the script. But I get the same error message as above when I run it via crontab. crontab -e cat /home/username/vuls/run_vuls_report.sh
|
I'm also suffering from the same issue since last wednesday.
|
The -it flag is required
|
Solved the problem of trying to read from STDIN and stopping on the way when running from CRON or AWS Lambda.
Solved the problem of trying to read from STDIN and stopping on the way when running from CRON or AWS Lambda.
Solved the problem of trying to read from STDIN and stopping on the way when running from CRON or AWS Lambda.
@Klar |
@kotakanbe |
Thank you @kotakanbe, the -it flag did the trick :) |
@kotakanbe I tried it with the -pipe command but couldn't get it to work, did you test it, if so how does your script / crontab look? thanks a lot |
@Klar |
@kotakanbe |
Hi,
if I run the current Docker container with the report parameter I always get this message:
time="Jan 15 01:38:55" level=error msg="Failed to read from JSON: Stdin is invalid: "
. No other output is created and no mail is sent.Environment
vuls v0.2.0 8e77937 (Docker-Image, Tag latest, Image ID af4a684f4a87)
Docker version 1.12.6, build 78d1802
Server: Debian 8.6
Command:
docker run --rm -v /home/service/vuls-data/ssh:/root/.ssh:ro -v /home/service/vuls-data/data/:/vuls -v /home/service/vuls-data/log/vuls/:/var/log/vuls -v /etc/localtime:/etc/localtime:ro vuls/vuls report -cvedb-path=/vuls/cve.sqlite3 -format-short-text -config=/vuls/config.toml -to-email -debug
The results directory is located directly within the mapped data directory. Have I missed something at the update to 0.2 or is this a bug?
The text was updated successfully, but these errors were encountered: