-
Notifications
You must be signed in to change notification settings - Fork 175
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-operator container 0.19.0 stop with: fatal error: stack overflow #1931
Comments
@aandreev-akamai release 0.19.0 has breaking changes, please follow steps on release-notes |
I have done these steps... forgot to mention it. |
can you please share your configmaps ? |
|
|
@aandreev-akamai can you please add the configmap of trivy, |
|
@aandreev-akamai its look like a bug in trivy, is this happen when scanning specific container, is it somthing you can share so Ill be able to reproduce Btw: do you have more logz with context that you can share, maybe set debug mode? |
Not sure if it is directly related to a specific container... |
about containers: after restart I got a few scaner Jobs still exist each time. But jaeger only installed on k8s cluster which has this issue. I hope it will help... |
thanks got it to reproduce with image |
@aandreev-akamai trivy issue aquasecurity/trivy#6360 |
Seems that trivy-operator:0.19.1 (helm chart version 0.21.1) has same issue:
|
After update deployment from the latest helm-chart ( 0.21.0 ) the trivy-operator container starts to crash with exit code 2
How I found in container logs:
trivy-logs.gz
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
): Server Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.9", GitCommit:"d15213f69952c79b317e635abff6ff4ec81475f8", GitTreeState:"clean", BuildDate:"2023-12-22T00:13:26Z", GoVersion:"go1.20.12", Compiler:"gc", Platform:"linux/amd64"}The text was updated successfully, but these errors were encountered: