Something went wrong scanning repository mlohr: Image not found - But image is there

Describe the bug After publishing a new version of one of my helm charts, I got an email “Something went wrong scanning repository mlohr” complaining

image not found: quay.io/k8scsi/csi-resizer:v0.3.0 (package hcloud-csi-driver:1.1.1)
image not found: quay.io/k8scsi/livenessprobe:v1.1.0 (package hcloud-csi-driver:1.1.1)

However, when I’m doing a manual docker pull, this works without any problems. Therefore, I suspect a problem with the image scanner or something similar. Since wrong warnings can lead to generally being ignored in future, even if then the image really cannot be found, I strongly suggest to take a look into this.

I’m not completely sure if it is actually a bug, but I still wanted to report and discuss with you why this happens and how I or you can prevent this from happen again.

To Reproduce I don’t know any reliable way to reproduce this problem. However, I got this warnings for two consecutive version updates of my helm chart.

Expected behavior If I am able to pull the image, the scanner should be able to pull as well. If there are connection problems/rate limitations of the scanner, it should not warn the helm chart owner but just try again later.

Screenshots Original mail screenshot:

[MatthiasLohr]

Didn’t know about that! Thanks for pointing out!

[tegioz]

No worries. You can already whitelist specific images so that they are not scanned for security vulnerabilities. This requires to provide the containers images manually using a special annotation in the Chart.yaml file. Please see the artifacthub.io/images annotation in https://artifacthub.io/docs/topics/annotations/helm/.