-
Notifications
You must be signed in to change notification settings - Fork 61
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
Failed to perform collection on k3s cluster nodes #594
Comments
This might be due to k3s containerd.sock path is not using the default value ( I am not familiar with k3s, but if there is a way to change path to default value for k3s, this should unblock you. |
Is it possible instead to expose the containerd path used by Eraser as a config value (i.e. in the helm values file)? |
@taliamax yes, we can add to backlog for path to be part of configmap. If you are interested in contributing, feel free to pick up this issue. |
Related #647 |
related aquasecurity/trivy#3599 for trivy support |
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
Attempted to install Eraser on cluster running k3s, and although the manager was able to successfully run, all collectors failed. This failed using both the manifest and the helm installation process, for versions
v0.5.0
andv0.4.0
, as well as for the manifest installationv1.0.0-beta.3
.All version experienced the same error logs on the collector pods:
What did you expect to happen:
Eraser to set up image cleaning
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
v0.4.0
,v0.5.0
,v1.0.0-beta.3
kubectl version
):Client Version: v1.25.2
Kustomize Version: v4.5.7
Server Version: v1.25.4+k3s1
The text was updated successfully, but these errors were encountered: