C3 AI Documentation Home

Registry Mirroring

C3 AI hosts all necessary images to deploy the C3 Agentic AI Platform on registry.c3.ai. If your organization uses its own registry instead of registry.c3.ai, registry mirroring ensures you pull all necessary images to deploy the platform. This topic discusses two ways you can mirror your own registry to match registry.c3.ai:

  • Follow your registry provider's documentation to automatically mirror registry.c3.ai with pull-through caching
  • Run a script to manually transfer images from registry.c3.ai to your own registry

C3 Agentic AI Platform images

For an exact list of images and their versions required for the platform, see Installation, Upgrade, and Patch Information for your platform version.

For information about each of the images, see Images Required for Installation and Deployment.

Automatically mirror registry.c3.ai

The following options are some registry solutions that support automatic mirroring. Refer to your registry provider's documentation to learn about your options for registry mirroring.

JFrog Artifactory

JFrog Artifactory offers the following registry mirroring options:

  • Docker repositories: Set up Docker repositories in JFrog Artifactory to proxy and cache Docker images from registry.c3.ai. This enables image pulling and maintains local copies for faster access and offline availability. See JFrog Artifactory Docker Repositories Documentation.
  • Remote repositories: Configure remote repositories in JFrog Artifactory to create proxy connections to registry.c3.ai. This approach allows you to locally cache images and automatically sync with the upstream registry. See JFrog Artifactory Remote Repositories Documentation.

Sonatype Nexus Repository

Sonatype Nexus Repository offers the following registry mirroring options:

  • Docker proxy repository: Nexus Repository supports Docker proxy repositories that can mirror registry.c3.ai automatically. Configure a Docker proxy repository that points to registry.c3.ai to enable pull-through caching. See Proxy Repository for Docker.
  • Repository groups: Create Docker repository groups that combine your proxy repository with hosted repositories for a unified endpoint. See Grouping Docker Repositories.

Harbor Registry

Replication rules: Harbor supports replication rules that can automatically sync images from registry.c3.ai to your local Harbor instance. Configure pull-based replication to keep your local registry synchronized. See Harbor Replication Documentation.

AWS Elastic Container Registry (ECR)

Pull through cache: ECR supports pull-through cache rules for upstream registries. Configure ECR to cache images from registry.c3.ai automatically when they are pulled. See AWS ECR Pull Through Cache Documentation.

Azure Container Registry (ACR)

Cache rules: ACR provides caching capabilities for external registries. Set up cache rules to automatically cache images from registry.c3.ai when accessed through your ACR instance. See Optimize image pulls with artifact cache in Azure Container Registry.

Manually transfer images

You can manually transfer images from registry.c3.ai to your own registry with a script. The following steps use images for platform version 8.8.9 as an example. Use the appropriate images and versions for your own platform deployment. See C3 Agentic AI Platform images for information about the required images.

  1. Create a .txt file that contains a list of the required images. Here's an example file:

  2. In the same directory where you stored the .txt file, run the following script. Replace <your_registry> with your own registry endpoint.

    This script automatically copies all images from registry.c3.ai to your private registry. It uses the Skopeo command line tool to copy container images between registries. However, you can use other Open Container Initiative (OCI)-compliant container image command line tools, such as Docker or Podman.

See also

Was this page helpful?