Connect Your Engine to an Image Registry - Administrator Guide - Cortex XSIAM - Cortex - Security Operations

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.

If you use an engine, you need to connect it to the registry before setting up Cortex XSIAM to pull images.

The following example describes connecting an engine to an authenticated Docker image registry. It 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 or podman-login.

When using an engine shell installer on a system that runs a Docker client, for example Ubuntu, the demisto user is created without a home directory. By default, the Docker client stores the Docker login credentials in the home directory, Therefore, you need to create a home directory if you are using the default Docker configuration.

You can run the following commands when logged in as root (or another privileged user).