DataRobot container images¶
The DataRobot platform uses Docker Hub as its primary container registry. While the DataRobot Helm chart is configured to use Docker Hub by default, it also supports using a dedicated private ACR container registry if required.
Note
For additional information about Docker Hub, see the Docker Hub documentation.
Using private Azure Container Registry (ACR)¶
You can install the DataRobot platform by pulling application images from either Docker Hub or a private Azure Container Registry (ACR). If you plan to use a private ACR Registry to store the DataRobot platform images, follow the steps listed below.
Set environment variables¶
To store configuration values, set the following variables (ensure that the below commands include the necessary context):
export DOCKERHUB_USERNAME="DATAROBOT_CUSTOMER_USERNAME"
export DOCKERHUB_PASSWORD="DATAROBOT_CUSTOMER_PASSWORD"
export DATAROBOT_VERSION="X.X.X"
export ACR_NAME="DESIGNATED_ACR_NAME"
export ACR_URL="${ACR_NAME}.azurecr.io"
export ACR_PASSWORD=$(az acr credential show --name $ACR_NAME --query "passwords[0].value" -o tsv)
Note
- Replace
DATAROBOT_CUSTOMER_USERNAMEandDATAROBOT_CUSTOMER_PASSWORDwith your Docker Hub credentials. You can request these credentials through the DataRobot Support Portal or by emailing support@datarobot.com. - Replace
X.X.Xwith the latest release chart version. - Replace
DESIGNATED_ACR_NAMEwith your actual ACR Name.
Optionally, set an additional prefix for OCI repository names:
export DATAROBOT_REPO_PREFIX="" # Optional: Set additional prefix for DataRobot repository names
Note
DataRobot images are prefixed with datarobot/ by default.
Initial setup¶
To authenticate your Docker Hub session, run the following command:
echo ${DOCKERHUB_PASSWORD} | docker login -u ${DOCKERHUB_USERNAME} --password-stdin
Download the main DataRobot chart from Docker Hub:
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 ${DATAROBOT_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 Azure ACR, run the following command:
az login
az acr update --name ${ACR_NAME} --admin-enabled true
Load images into ACR¶
Load images into your private registry by pulling DataRobot images from Docker Hub:
[ -z "${DATAROBOT_REPO_PREFIX}" ] || export PREFIX_ARG="--prefix ${DATAROBOT_REPO_PREFIX}"
helm datarobot sync datarobot-prime-${DATAROBOT_VERSION}.tgz ${PREFIX_ARG} -r ${ACR_URL} -u ${ACR_NAME} -p "${ACR_PASSWORD}"
If it is a restricted network, you can load images using the compressed tarball artifact:
[ -z "${DATAROBOT_REPO_PREFIX}" ] || export PREFIX_ARG="--prefix ${DATAROBOT_REPO_PREFIX}"
helm datarobot load tarball-datarobot-${DATAROBOT_VERSION}.tar.zst ${PREFIX_ARG} -r ${ACR_URL} -u ${ACR_NAME} -p "${ACR_PASSWORD}"
Verify images are in ACR¶
To verify that the repositories have been created and the images are loaded into Azure ACR, use the following commands.
To get a list of repositories containing a specific name:
az acr repository list -n ${AZ_ACR_NAME}
Below is an example output:
[
...
"AZ_ACR_REPO/build-service",
"AZ_ACR_REPO/datarobot/ai-application-engine",
"AZ_ACR_REPO/datarobot/datarobot-portable-prediction-api",
"AZ_ACR_REPO/datarobot/datarobot-runtime",
...
]
To get specific information about the manifests for a given repository use a command like the below example:
az acr repository show-manifests -n ${AZ_ACR_NAME} --repository AZ_ACR_REPO/datarobot/datarobot-runtime
The output of the above example:
[
{
"digest": "sha256:c2a106997ecc6a4c9b6da591410b1301943525b1586905182cc7b7c57c8da89b",
"tags": [
"x.x.x"
],
"timestamp": "2023-05-23T18:05:15.8912361Z"
}
]