Self-managed installation and maintenance > Installation and configuration guide > Server preparation > DataRobot container images

DataRobot container images¶

The DataRobot application uses Docker Hub as its primary container registry. While the DataRobot Helm chart is configured to use Docker Hub by default, it also supports the option to use a dedicated private container registry if required.

Note

For additional information about Docker Hub, see the Docker Hub Documentation.

Private registry overview¶

To begin, download the main DataRobot chart.

export DOCKERHUB_USERNAME="DATAROBOT_CUSTOMER_USERNAME"
export DOCKERHUB_PASSWORD="DATAROBOT_CUSTOMER_PASSWORD"
echo $DOCKERHUB_PASSWORD | helm registry login registry-1.docker.io -u $DOCKERHUB_USERNAME --password-stdin
helm pull oci://registry-1.docker.io/datarobot/datarobot-prime --version X.X.X

Note

Replace DATAROBOT_CUSTOMER_USERNAME and DATAROBOT_CUSTOMER_PASSWORD with your Docker Hub credentials. You can request these credentials through the DataRobot Support Portal or by emailing support@datarobot.com.
Replace X.X.X with the latest release chart version.

The process of loading images into your private registry is handled by a dedicated Helm plugin. To install the plugin, use the following command:

helm plugin install https://github.com/datarobot-oss/helm-datarobot-plugin.git

To authenticate your Docker Hub session, run the following command:

echo $DOCKERHUB_PASSWORD | docker login -u $DOCKERHUB_USERNAME --password-stdin

Option 1: Load all images using the datarobot-prime Helm chart. Replace the environment variables with your Google Cloud project values.

export PREFIX="${GCP_PROJECT_NAME}/${GAR_REPO}"
helm datarobot sync datarobot-prime-x.x.x.tgz -r "${GCP_REGION}-docker.pkg.dev" --prefix $PREFIX -u _json_key_base64 -p "${GCP_BASE64_SERVICE_ACCOUNT_KEY}"

Option 2: Load all images using the compressed tarball artifact. Replace the environment variables with your Google Cloud project values.

export PREFIX="${GCP_PROJECT_NAME}/${GAR_REPO}"
helm datarobot load tarball-datarobot-x.x.x.tar.zst -r "${GCP_REGION}-docker.pkg.dev" --prefix $PREFIX -u _json_key_base64 -p "${GCP_BASE64_SERVICE_ACCOUNT_KEY}"

Verify images are in a Docker registry¶

To verify that the images have loaded into your registry, you can run a curl command to pull the registry catalog. The URL format is http{s}://DOCKER_REGISTRY_URL/v2/_catalog.

The example below shows a curl command to a registry with basic authentication. Replace the placeholders with your registry's details.

curl -k -u DOCKER_REGISTRY_USERNAME:DOCKER_REGISTRY_PASSWORD https://DOCKER_REGISTRY_URL/v2/_catalog

The response is a JSON formatted list of the images in the registry, similar to the following:

{
  "repositories": [
    "build-service",
    "datarobot/ai-application-engine",
    "datarobot/datarobot-runtime",
    "datarobot/operator-lrs",
    "image-builder",
    ...
  ]
}