-
Notifications
You must be signed in to change notification settings - Fork 91
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
[Bug] PDF Report is not fixed #268
Comments
@rudnypc If you don't fill out the bug template completely we won't be able to help you. |
Hi there, I have the same issue in 21.4.3-v1 image. |
This work for me #249 (comment) |
It looks badly like a memory shortage on the build system, because this never happened on a 16GB ram system and only on the GitHub servers… with ~2GB ram.
Von meinem iPhone gesendet
… Am 22.09.2021 um 16:38 schrieb SOC-LaneWan ***@***.***>:
Hi there, I have the same issue in 21.4.3-v1 image.
This worked for me too. #249 (comment)
Had the same issue.
Thanks 👍
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I don't think this is related to RAM limitations. My system has 24GB of RAM, running only this container and I'm getting the same 0 byte issue when exporting PDF. |
Ok!
|
Doesn't make sense... It's already listed here. |
I merge that fix with all entrypoint code after that I mapped the entrypoint file to /entrypoint.sh . |
@rudnypc How do you map the entrypoint file? |
Nevermind, I got it guys. I ran the line |
Have switch to Debian. Closing this. |
We have found another bug that related to the PDF Reports that we track on DeineAgenturUG/greenbone-gvm-openvas-for-docker#9 |
Hi,
When I try to download a PDF report, the report is 0 bytes, I'm using the image "21.4.3-v1-data-full".
I have to run that command:
#249 (comment)
DOCKERHUB
MY STACK:
The text was updated successfully, but these errors were encountered: