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.
Configure image registry
Go to Settings → Configurations → General → Image Registry.
Set Use Additional Private Image Registry to On.
Configure access to the private image registry and the images to pull.
Select Connection, then select Direct or Using Engine.
Define the Registry URL.
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.
If you selected Direct, set the Username and Password/Access Token.
Select Test to verify the registry connection.
Define Import images in
name:tagformat. For example:myimage:2.7.18.24398.Add, edit, or remove images. If you do not specify a tag, the default
latesttag is added automatically.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.
Last updated
Was this helpful?
