You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The output of the scan is likely very large, so I would recommend breaking it into multiple smaller scans if you want to limit memory usage. May I ask, around how many individual hosts are you targeting with your scan to reach 8.9GB?
If the number is low, then the issue might lie somewhere else.
Hi @Ullaakut, the scan does target a large number of hosts (hundreds), however, when running not in a container, I tried to scan several times more hosts, and the memory consumption was several times less.
Mh that's interesting 🤔 Maybe it's an issue with the nmap/curl versions used in the container? Or maybe there is some memory overhead to outbound connections from the container, which absolutely could make sense.
Are you running Docker natively or through Docker for Mac / Docker for Windows ?
Even without using Progress() the memory usage is incredible when running in container.
Any possible solutions?
The text was updated successfully, but these errors were encountered: