Private Container Registry

Clients can also use their own container image registry to control the images they are using in production.

Trisotech offers three container images

Image

Description

registry.trisotech.com/des/platform

The Digital Enterprise Suite image. It contains the modeling and automation capabilities.

registry.trisotech.com/des/scripts

The Maintenance Scripts cron jobs for backup and clean up for the Digital Enterprise Suite.

registry.trisotech.com/des/engine

The base image for Digital Distributed Containers. It contains the automation ability and requires an additional image layer with the published models to be executable.

Installing the Digital Enterprise suite requires the registry.trisotech.com/des/platform and registry.trisotech.com/des/scripts container image and building Digital Distributed Containers require the registry.trisotech.com/des/engine base image. You may want to transfer only some of those images to the private registry depending on the chosen deployment scenario.

Transfer the container images

You first need to authenticate using docker to the Trisotech registry.

docker login registry.trisotech.com -u license -p <LICENSE>

Replace <LICENSE> with the Trisotech license (DES or DDC) to authenticate.

Pull the images from the Trisotech Registry

docker pull registry.trisotech.com/des/platform:v<VERSION>
docker pull registry.trisotech.com/des/engine:v<VERSION>
docker pull registry.trisotech.com/des/scripts:latest

The <VERSION> is replaced by X.X.X but Trisotech tags its container images with a lower case v before X.X.X. ex: The DES container image for version 12.0.0 is tagger v12.0.0 in the container registry.

Tag the images with the private registry

docker tag registry.trisotech.com/des/platform:v<VERSION> <PRIVATE_REGISTRY>/des/platform:v<VERSION>
docker tag registry.trisotech.com/des/engine:v<VERSION> <PRIVATE_REGISTRY>/des/engine:v<VERSION>
docker tag registry.trisotech.com/des/scripts:latest <PRIVATE_REGISTRY>/des/scripts:latest

Push the images to the private registry

docker push <PRIVATE_REGISTRY>/des/platform:v<VERSION>
docker push <PRIVATE_REGISTRY>/des/engine:v<VERSION>
docker push <PRIVATE_REGISTRY>/des/scripts:latest

Using the private registry when installing the Digital Enterprise Suite

Add the following two lines to the installation of the Digital Enterprise Suite:

--set image.pullSecrets=<PULL_SECRET> \
--set image.repository=<PRIVATE_REGISTRY>/des/platform
--set maintenanceImage=<PRIVATE_REGISTRY>/des/scripts:latest

You need to create a pull secret in the des namespace and replace its name in <PULL_SECRET>.

Using the private registry when building Digital Distributed Containers

For the Digital Distributed Container, the engine base image needs to be configured in the admin section Digital Distributed Container of the Digital Enterprise Suite as the Base image for containers. You will also need to configure proper authorization for the registry.