-
Notifications
You must be signed in to change notification settings - Fork 13
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
Scanner - Could not get a bpf #15
Comments
I tried to build it again with the tag > 21.4.0-v5
|
This looks like you have to run the docker image in privileged mode. or even more rights. |
Hi @Dexus
There has been no change, still getting the same behavior. Do we change permission on the somewhere else as well ? |
@karnamonkster please contact greenbone via community. I think the problem is that openvas is not up2date and I will create a new version. Other thing: which network mode you use for the container? |
Hi @Dexus , |
@karnamonkster will give you a notice when its done, need some more tasks first to be done. |
For further support, use https://github.com/DeineAgenturUG/greenbone-gvm-openvas-for-docker |
@karnamonkster I think I found the problem and will check this over the weekend. When I'm right with what I think, it will be available via https://github.com/DeineAgenturUG/greenbone-gvm-openvas-for-docker in the next week |
@karnamonkster please try to set a example: maybe also add I used it together with a custom ipvlan to match my LAN network. |
Hi,
I am using the OpenVAS scanner - 21.4.0-v5 (latest image)in a remote deployment
The scanner registration is completed.
Scanner gets the tasks and starts the scan on the Target.
However there are logs which state the tests are failing and hence the final report does not include expected findings as well.
Sample loglines within /var/log/gvm/openvas.log
Appreciate if there is anything we could do to fix this.
The text was updated successfully, but these errors were encountered: