> 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-xsoar-8-on-prem/8.10/configure-cortex-xsoar/integrations/change-the-docker-image-in-an-integration-or-script/connect-your-engine-to-an-image-registry.md).

# Connect your engine to an image registry

Connect an engine to an authenticated image registry in Cortex XSOAR 8.10 On-prem.

Using an engine to communicate with an image registry streamlines deployment by managing dependencies, ensuring version control, and facilitating scalability, load balancing, and secure access to private images.

To use an engine, you need to connect the engine to an authenticated Docker image registry and then set it up in the tenant.

{% hint style="info" %}

### Note

This procedure uses the `--username` and `--password` command line options to pass the username and password directly. For environments where command history or logs are visible to others, consider more secure methods like Docker configuration files for handling authentication in production or CI/CD environments. For more details, see [docker login](https://docs.docker.com/engine/reference/commandline/login/) or [podman-login](https://docs.podman.io/en/stable/markdown/podman-login.1.html).
{% endhint %}

1. Open a terminal on the machine where your engine is running.
2. Run `docker login` with username and password.

   ```programlisting
   docker login --username=<your-username> --password=<your-password> <registry-url>
   ```

   Replace `<your-username>`, `<your-password>`, and `<registry-url>` with your Docker registry credentials and the URL of your Docker image registry.
3. (Optional) Search for or pull a Docker image.

   After logging in successfully, you can optionally validate access to images by searching for an image or pulling an image from the registry to your local machine using the `docker search` or `docker pull` command.

   ```programlisting
   docker search <registry-url>/<image-name>:<tag>
   docker pull <registry-url>/<image-name>:<tag>
   ```

   Replace `<registry-url>`, `<image-name>`, and `<tag>` with your registry URL, the name of the Docker image, and the image tag, respectively.
4. In the tenant, set up the engine to pull images from a private image registry.


---

# 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-xsoar-8-on-prem/8.10/configure-cortex-xsoar/integrations/change-the-docker-image-in-an-integration-or-script/connect-your-engine-to-an-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.