The number of NVTs has not grown significantly since 2021-07-02.
However, when creating a new container from the very same image (and subsequently, downloading the feed for the first time in the new container) I have detected that the number of NVTs is way larger (around 76000 NVTs).
Describe the bug
Dear all,
Initially I detected the following situation:
When parsing the gvmd.log file in order to list the feed updates (and the corresponding number of NVTs) I found what follows:
The number of NVTs has not grown significantly since 2021-07-02.
However, when creating a new container from the very same image (and subsequently, downloading the feed for the first time in the new container) I have detected that the number of NVTs is way larger (around 76000 NVTs).
As a consequence of this I have attempted to force update the NVTs by hand as shown by @pixelsquared in https://github.com/Secure-Compliance-Solutions-LLC/GVM-Docker/discussions/147#discussioncomment-548518, using the command:
What I see in the logs is the following:
All files seem to be in place:
Additionally, when logged in the docker container:
To Reproduce
Expected behavior I suppose I should not get those #Permission denied (13) logs
Host Device:
Image in use:
docker image inspect <image>
: