|
Important
| This is not a universal list of requirements. Please be sure to also review the documentation for your target deployment environment for any additional prerequisites. |
To install Domino, you must have the following:
-
quay.io credentials provided by Domino.
-
Docker installed and the daemon running on your local machine.
-
Helm installed.
-
Kubectl installed.
-
Kubectl access to the cluster where you’ll deploy Domino.
-
-
Access to Docker images for Domino components.
-
Access to Helm charts.
-
The ddlctl command line installed.
|
Important
|
Newer versions of Docker Desktop changed a default setting that blocks access to the default Docker socket, which ddlctl depends on for some operations.
Verify that you have enabled Allow the default Docker socket to be used under Advanced Settings before continuing.
|
To retrieve images of Domino components, the target cluster must have access to the following domains:
-
quay.io -
domino.tech -
k8s.gcr.io -
docker.elastic.co -
docker.io -
gcr.io
If you intend to install Domino offline, configure your Domino custom resource definition specification to point to a private Docker registry and application registry.
Offline installation packages are downloaded from the mirrors.domino.tech domain.
Domino recommends that you use a partition with at least ten times more disk space than the total volume of your container images. For example, if your container images occupy several dozen gigabytes, use a partition with several hundred gigabytes of space available. This ensures that the partition has enough free space for container images that Domino users create and manage. See Why did my execution fail with the error 'No space left on device'? for advice if you exceed your available disk space.