Prisma Cloud twistcli scan fails pulling the image - check registry auth, URL, and tag

TL;DR

Common causes: missing registry authentication (add a login step before the scan); the imageregistry input does not match the actual registry URL; the imagetag is wrong or the tag does not exist; the runner cannot reach the registry (network).

Steps

1. Per the Prisma Cloud scan workflow: verify registry login, registry URL, and tag before re-running the scan.

When to use

You are seeing this: Per the Prisma Cloud scan workflow: verify registry login, registry URL, and tag before re-running the scan. Use this skill when you run into "Prisma Cloud twistcli scan fails pulling the image - check registry auth, URL, and tag".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Problem: The CI scan step fails before scanning starts, at image pull. Common causes: missing registry authentication (add a login step before the scan); the imageregistry input does not match the actual registry URL; the imagetag is wrong or the tag does not exist; the runner cannot reach the registry (network). Verify each in order before re-running - the action surfaces which of these it hit.

Verified resolution: Per the Prisma Cloud scan workflow: verify registry login, registry URL, and tag before re-running the scan.

Source URL: https://github.com/solacedev/solace-public-workflows/blob/HEAD/prisma-cloud-scan/README.md