Skip to content
This repository has been archived by the owner on Oct 14, 2024. It is now read-only.

Fresh Install - Unable to parse image id #667

Open
psleep opened this issue Feb 21, 2024 · 2 comments
Open

Fresh Install - Unable to parse image id #667

psleep opened this issue Feb 21, 2024 · 2 comments

Comments

@psleep
Copy link

psleep commented Feb 21, 2024

Hi,
I have deployed kubeclarity via helm as a test. Pods are running and healthy, I can access the UI but whenever I try to scan anything (using the default grype scanner) I get the following:

logs.txt

This is a fresh install of the latest version (v2.23.1)
Kubernetes installed via kubeadm (v1.29)
CRIO runtime v1.28

DNS and networking is fine on my cluster, there are no network policies applied to the kubeclarity namespace
Do you have any pointers or suggestions?

Thanks!

@psleep
Copy link
Author

psleep commented Feb 23, 2024

This issue is due to container runtimes.
CRIO uses imageID to store the hash, containerd has the expected format in imageID

@andreiPtr
Copy link

andreiPtr commented Jul 15, 2024

@psleep Found a way to fix this? Having the same issue

@ramizpolic ramizpolic changed the title Fresh Install - Unable to parse image id [kubeclarity] Fresh Install - Unable to parse image id Aug 8, 2024
@ramizpolic ramizpolic transferred this issue from openclarity/openclarity Aug 8, 2024
@ramizpolic ramizpolic changed the title [kubeclarity] Fresh Install - Unable to parse image id Fresh Install - Unable to parse image id Aug 10, 2024
@ramizpolic ramizpolic transferred this issue from another repository Aug 10, 2024
@ramizpolic ramizpolic removed this from OpenClarity Aug 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants