> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/automations/scripts/change-the-docker-image-in-an-integration-or-script/pull-docker-images-from-a-private-image-registry.md).

# Pull Docker images from a private image registry

Pull private registry images for Cortex XSIAM.

Pulling images from a private image registry enables securely accessing and deploying content, for example, custom integrations containing scripts and code packaged into Docker images. You can then run the integrations and scripts.

### Before you begin

* Before pulling a custom image ensure the image does not infringe any licenses.
* If using an engine, connect the engine to the private image registry using Docker or Podman. See [Connect an engine to an image registry](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/automations/scripts/change-the-docker-image-in-an-integration-or-script/connect-an-engine-to-an-image-registry.md).

{% hint style="info" %}
(Multi-tenant) This feature is not supported on the Main Account.
{% endhint %}

### Configure image registry

1. Go to **Settings** → **Configurations** → **General** → **Image Registry**.
2. Set **Use Additional Private Image Registry** to **On**.
3. Configure access to the private image registry and the images to pull.
   1. Select **Connection**, then select **Direct** or **Using Engine**.
   2. Define the **Registry URL**.

      <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Set the registry URL to your organization registry service hostname, such as <code>us-central1-docker.pkg.dev</code>.</p></div>
   3. If you selected **Using Engine**, select the engine to use. Authentication is set on the engine machine, not in the tenant. For an example, see [Connect an engine to an image registry](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/automations/scripts/change-the-docker-image-in-an-integration-or-script/connect-an-engine-to-an-image-registry.md).
   4. If you selected **Direct**, set the **Username** and **Password/Access Token**.
4. Select **Test** to verify the registry connection.
5. Define **Import images** in `name:tag` format. For example: `myimage:2.7.18.24398`.
6. Add, edit, or remove images. If you do not specify a tag, the default `latest` tag is added automatically.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>If you use folders to store images, include the folder path in the image name, such as <code>myorg/python:latest</code>. Only one folder is supported. Subfolders are not supported.</p><p>The <code>demisto/</code> prefix cannot be used for custom registry images.</p></div>
7. Select **Save** to save the configuration and start synchronization.

### Image synchronization

When you click **Save** or **Update Docker Images**, Cortex XSIAM performs synchronization, which involves:

* Pulling the images from the external registry.
* Copying and storing the images on the platform.
* Updating the engines with the new images.

The synchronization process may take time. The **Image Registry** page displays synchronization status (for example in progress, complete, failure).

If the engine fails to synchronize, it may be offline. When it goes back online, it will pull any new images when running scripts or integrations that use them.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/automations/scripts/change-the-docker-image-in-an-integration-or-script/pull-docker-images-from-a-private-image-registry.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
