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
trivy k8s: --timeout flag #6304
Labels
kind/bug
Categorizes issue or PR as related to a bug.
target/kubernetes
Issues relating to kubernetes cluster scanning
Comments
chen-keinan
added
kind/bug
Categorizes issue or PR as related to a bug.
target/kubernetes
Issues relating to kubernetes cluster scanning
labels
Mar 12, 2024
@vintury is this has been running in ci pipeline ?
Do you mind doing the same test on local cluster and let me know the results ? |
but I think this is not related to my problem |
this issue should be fixed with latest trivy |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Categorizes issue or PR as related to a bug.
target/kubernetes
Issues relating to kubernetes cluster scanning
Discussed in #6260
Originally posted by vintury March 4, 2024
Description
When the flag '--timeout' is use the scan don't finish in selected timeout.
I'm guessing the problem is caused by containers not being able to download.
Desired Behavior
A few days later I see that the process is still running.
Scan don't finish after 160m.
Actual Behavior
Stop process after timeout exists.
Reproduction Steps
1. Create namespace with fiew southand pods. I have about 280 Pods and 738 images (86 from dockerhub). 2. Run trivy k8s with flag --timeout 160m 3. Scan don't finish after 160m.
Target
Kubernetes
Scanner
Vulnerability
Output Format
Table
Mode
Standalone
Debug Output
Operating System
CentOS Linux release 7.9.2009 (Core)
Version
# ./trivy --version Version: 0.49.1
Checklist
trivy image --reset
The text was updated successfully, but these errors were encountered: