How to configure trivy operator with helm chart with a different path for the containerd socket. #2352
Unanswered
sarg3nt
asked this question in
Help & Support
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Our OS stores the containerd socket in
/run/k3s/containerd/containerd.sock
and I can't figure out how to tell Trivy where the socket is with the Helm chart.I've looked here and found one other question where someone ran into the same thing but they didn't actually say how they fixed it.
I see the docs that say we can set
CONTAINERD_ADDRESS
but there does not appear to be a way to setenv
vars in the Helm chart.Here's the error we are getting.
Beta Was this translation helpful? Give feedback.
All reactions