Private or offline installation

Domino provides bundles of offline installation media for when you use fleetcommand-agent without Internet access to upstream sources of images and charts. To serve these resources, you must have a Docker registry accessible to your cluster.

Downloads

URLs of available offline installation bundles are in the release notes. You can download these bundles using the curl command with basic authentication. If there are network connectivity issues you can use the wget command with the --continue or -c option. Contact your Domino account team for credentials.

Note
 The versioned collection of images (named docker-images-{4.4}.tar) contains all required images for this type of deployment and must be the only downloaded file.

Example curl download:

curl -u username:password -#SfLOJ https://mirrors.domino.tech/s3/domino-artifacts/offline/fleetcommand-agent-v44/docker-images-5.x.x.tar

Example wget download:

wget -c --user domino-registry --password xxxxxxx https://mirrors.domino.tech/s3/domino-artifacts/offline/fleetcommand-agent-v44/docker-images-5.x.x.tar

Extract and load

The images bundle is a .tar archive that must be extracted before you use it.

tar -xvf docker-images-5.x.x.tar

In the docker-images bundle there will be:

  • a collection of individual Docker image .tar files

  • a images.json metadata file

  • a domino-load-images.py script

domino-load-images.py is a script to ingest the images.json metadata file and load the associated Docker images for a specific Domino version into the given remote Docker registry.

To load images into your private registry, run domino-load-images.py and pass in the URL of your registry as an argument. The script expects to run in the same directory as the images.json metadata file and the .tar image files.

Example:

python domino-load-images.py your-registry-url.domain:port

Once images have been loaded into your private registry you’re ready to install Domino.

Install

To install Domino with a custom registry, the image references must be modified to reference the upstream registry. Use the --image-registry argument on the init command to modify all image references to the external registry.

docker run --rm -v $(pwd):/install quay.io/domino/fleetcommand-agent:v44
init --image-registry your-registry-url.domain:port --full --file /install/domino.yml

If your registry requires authentication, ensure the private_docker_registry section of your installer configuration is filled in with the correct credentials:

private_docker_registry:
  server: your-registry-url.domain:port
  username: '<username>'
  password: '<password>'

Helm 3

Charts come prepackaged within the fleetcommand-agent image. Set up the helm object in configuration to match the following:

helm:
  host: gcr.io
  namespace: domino-eng-service-artifacts
  username: ''
  password: ''
  insecure: false

Configuration

When you install Domino offline, there are a few main central configuration keys that must be re-pointed to the private registry that hosts the referenced images. From the Domino index page, click Admin in the main menu. Then in the administration portal, click Advanced > Central Config. Use the Add Record button at top right to add the following records:

KeyValue

com.cerebro.domino.builder.image

IMAGE_URI of the latest domino/builder-job

com.cerebro.domino.computegrid.kubernetes.executor.imageName

IMAGE_URI of the latest domino/executor

com.cerebro.domino.modelmanager.harnessProxy.image

IMAGE_URI of the latest domino/harness-proxy