For the complete documentation index, see llms.txt. This page is also available as Markdown.

Container

These settings apply to Custom Scan steps when both of these conditions are true:

  1. The policy_type is orchestratedScan or dataLoad.

  2. The scan_type is containerImage.

Container type

Key

container_type

Value

The registry type where the image is stored. Specify one of the following:

Scan a local image built and stored within the context of the current stage (via /var/run/docker.sock registered as a stage level volume mount).

local_image

A registry that uses the Docker Registry v2 API such as Docker Hub, Google Container Registry, or Google Artifact Registry.

JFrog Docker Registry.

Amazon Container Registry.

Container domain

Key

Value

The URL of the registry that contains the image to scan. Examples include:

Container project

Key

Value

The image name. For non-local images, you also need to specify the image repository. Example: jsmith/myalphaservice

Container tag

Key

Value

The image tag. Examples: latest, 1.2.3

Container access Id

Key

Value

Your access Id to the image registry.

Container access token

Key

Value

The password or access token used to log in to the image registry. In most cases this is a password or an API key.

You should create a Harness text secret with your encrypted token and reference the secret using the format <+secrets.getValue("container-access-id")>. For more information, go to Add and Reference Text Secrets.

AWS region

Key

Value

The region where the image to scan is located, as defined by the cloud provider such as AWS.

Last updated

Was this helpful?