# The \`Could not scan image vulnerabilities\` message when scanning images

**URL:** https://forums.k8slens.dev/t/the-could-not-scan-image-vulnerabilities-message-when-scanning-images/84
**Category:** FAQ
**Tags:** images, lens-desktop
**Created:** [January 30, 2023, 12:02pm UTC](https://forums.k8slens.dev/t/the-could-not-scan-image-vulnerabilities-message-when-scanning-images/84 "2023-01-30T12:02:10Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![dzhigzhitzhapov](https://forums.k8slens.dev/user_avatar/forums.k8slens.dev/dzhigzhitzhapov/32/189_2.png) [@dzhigzhitzhapov](https://forums.k8slens.dev/u/dzhigzhitzhapov)
#### Post date: [January 30, 2023, 12:02pm UTC](https://forums.k8slens.dev/t/the-could-not-scan-image-vulnerabilities-message-when-scanning-images/84/1 "2023-01-30T12:02:10Z")

</div>

The following items might help you to solve the image scanning issue:

1. If your image is in a registry that requires username and/or password, make sure that the `imagePullSecret` is present on the pod.
2. Make sure the [vulnerability database](https://ghcr.io/) from GitHub Packages is accessible. Check your operating system proxy settings if needed.
3. Make sure that the image registry URL is accessible.