> 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.md).

# Change the Docker image in an integration or script

Docker enables you to run scripts and integrations from an image in a controlled environment that isolates and safeguards the tenant. It also simplifies environment setup by packaging dependencies and configurations within an image, ensuring consistent execution across different systems. By default, Cortex XSIAM pulls images from the `Demisto` Docker image registry in GitHub, which are used in scripts and integrations as needed. Cortex XSIAM integrations and scripts have the relevant Docker image already selected. For example, the Rasterize integration uses the `demisto/python.3.3.11.9.1079` Docker image.

You may want to select a different Docker image for your integration or script. In Cortex XSIAM, you can select a different Docker image from a dropdown that is pulled from the `Demisto` Docker image registry. In GitHub, the [dockerfiles-info branch](https://github.com/demisto/dockerfiles-info/tree/master) contains information about each image to help you find one that is relevant.

{% hint style="info" %}
You can access publicly available Docker images from the Cortex XSIAM tenant even if there is no external connection to the `Demisto` registry, for example, if due to firewall constraints, your engine cannot access the `Demisto` registry.
{% endhint %}

Change the Docker image for a script

1. Edit the script.
2. Under ADVANCED, in the Docker image name field, click X to clear the current selection and then select a Docker image name from the dropdown menu.

   For more information about changing the Docker image for a script, see the Advanced tab in [Create a script](/cortex-xsiam/configure-cortex-xsiam/automations/scripts/create-a-script.md).
3. Save your changes.

Change the Docker image for an integration

1. Navigate to Settings → Data Sources & Integrations, find and select your integration and edit the integration’s source.

   For an out-of-the-box content pack integration, you first need to duplicate the integration to edit it.
2. In the Integration Settings, expand the Script section.
3. Click X to clear the current selection and select a Docker image name from the dropdown menu.

   For more information about changing the Docker image, see the Advanced tab in [Create a script](/cortex-xsiam/configure-cortex-xsiam/automations/scripts/create-a-script.md).
4. Save your changes.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.