Closed DRIgnazGortngschirl closed 2 years ago
I feel stupid, but for all other which also face this issue.
Stop the container, remove all volumes and images and start it again, this should solve it.
In my case with docker compose
docker-compose stop
docker-compose rm
docker system prune
Using the latest docker image there seeems to be a issues with starting the scans as the are requested go imediatly in the state stoped even do the vulnerability scan starts in the backend.
System resources: 8 Cores 32 GB RAM 64 GB SSD Disk
IPs Hosts and Names where removed from the logs and replaced with placeholders.