Scan Error Codes
Here are possible error codes that may be returned at scan time. You can search for images by the error code using the search token scanErrorCode.
| Error Code | Description | Remediation |
|---|---|---|
| CMS-1300 | Undefined Error | Check network connectivity to the Qualys Enterprise TruRisk™ Platform. |
| CMS-1301 | docker login failure | Verify docker login credentials. |
| CMS-1302 | docker pull failure | Verify docker pull <image name>. |
| CMS-1303 | shell not found | Please refer to the Container Security User Guide for supported versions. |
| CMS-1306 | Failed to get the package manager for OS i.e. no supported package manager found | Please refer to the Container Security User Guide for supported versions. |
| CMS-1307 | Failed to save the container image | Check the available disk space on the host. |
| CMS-1308 | Found unsupported container image layer file format | Please refer to the Container Security User Guide for supported versions. |
| CMS-1309 | No OS information found for container image | The OS information is not present in the container image. |
| CMS-1310 | Failed to untar the container image | Check the available disk space on the host. |
| CMS-1311 | Package manager not found for the container image | The package manager is not present in the container image. |
| CMS-1312 | Unsupported OS detected for the container image | Please refer to the Container Security User Guide for supported versions. |
| CMS-1313 | docker pull failure: manifest not found | Verify docker pull <image name>. |
| CMS-1314 | docker pull failure: unknown blob | Verify docker pull <image name>. |
| CMS-1315 | docker pull failure: windows docker image | Verify docker pull <image name>. |
| CMS-1316 | docker pull failure: tls handshake failure | Verify docker pull <image name>. |
| CMS-1317 | docker pull failure: no space left on device | Clean up space on the container host to pull the image to scan. |
| CMS-1318 | docker pull failure: internal server error | Verify docker pull <image name>. |
| CMS-1319 | docker pull failure: docker pull rate limit reached | Verify the public registry image pull limit |
| CMS-1320 | Upload secret detection result failure | Verify network connectivity from the sensor host to the Qualys platform (proxy/firewall/load-balancer rules, allow-lists). Confirm the platform is reachable and the sensor is provisioned/authenticated. |
| CMS-1321 | Upload malware detection result failure | Verify network connectivity from the sensor host to the Qualys platform (proxy/firewall/load-balancer rules, allow-lists). Confirm the platform is reachable and the sensor is provisioned/authenticated. |
| CMS-1322 | Malware setup failure | Confirm the malware-scan feature is properly configured/enabled and that the required components and resources (disk, memory, dependencies) are available on the sensor host. |
| CMS-1323 | Failed to create image tar, no space left on device | Ensure adequate space for the largest images being scanned. |
| CMS-1324 | Failed to extract an image layer | Verify the image layers are intact (re-push if corrupted) and that the sensor host has sufficient disk space and permissions |
| CMS-1325 | Image pull failure: timed out in 1800 sec | Check network bandwidth/latency between the sensor host and the registry, and the image size. For very large images or slow links, ensure stable, high-throughput connectivity along with a higher timeout value. |
| CMS-1326 | Maximum allowed scan time exceeded | Typically caused by very large/complex images or resource contention. Ensure adequate CPU/memory/disk on the sensor host and reduce concurrent scan load. |
| CMS-1327 | Valid storage driver not found | Ensure the container runtime uses a supported storage driver. |