Run Docker image

If you need to test your Docker image before using it as the base for your builds, you can use the Run Image action:

Image loading...

Configuration

The action lets you use images created by preceding Docker build actions in the pipeline, or pull the image from the selected Docker registry.

Image Location

You can choose the source of your Docker image:

• Public registry: Pull images from public registries

  • Registry: Choose between Docker Hub or Other. If you select Other, you will need to provide the Registry URL (e.g., registry.dockerhub.com)
  • Image: Specify the image name (e.g., library/nginx, library/node)
  • Version: Set the image tag (e.g., latest, 24.0.2)

• Private registry: Use images from private registries (requires authentication)

  • Registry: Choose from Docker Hub, Amazon ECR, Google GCR, Google Artifact Registry, GitHub Container Registry, or Other
  • Integration: Choose the configured integration for authentication
  • Image: Specify the private image name
  • Version: Set the image tag

• From action: Use images created by previous actions in the pipeline

Selection Method

When using "From action", you can specify:

• Previous action: Automatically use the image from the most recent action
• Fixed: Choose a specific action by name

Options

In the Options tab, you can configure additional settings:

• Reset default image entrypoint: Override the default entrypoint of the image
• Don't cache image between runs: Force pulling a fresh image on each run
• Export container's filesystem as .tar archive: Save the container's filesystem as an artifact. When enabled, a Path field appears where you can specify the directory to export (e.g., /)

Additional Settings

• User: Specify the user to run the container as (optional)
• Image entrypoint: Override the default entrypoint command (optional)
• Image command: Define the command to execute inside the container (optional)

Image loading...

Cache and Repository

The Cache tab lets you define the mount path for the pipeline's filesystem. The filesystem contains the repository in the recently executed revision, together with the artifacts built in the previous steps of the pipeline. This solution allows our Docker image to operate on repository files.

Image loading...

YAML and API

• YAML configuration - Dockerfile linter configuration via YAML
• REST API - adding actions via API