Skip to main content
Tungsten Operator

Downloading the Provided Images

You should download the Tungsten Operator package file and the Docker image files from the Continuent Software Download portal, using your credentials. If you do not have access, contact Continuent Support.

All of the images are available for either Intel (amd64) or ARM (arm64) architecture and the filenames indicate this accordingly.
The examples below use the Intel architecture files.

Tungsten Operator Package​

You will need to first download the latest Tungsten Operator package and copy and unpack the file into the /opt/continuent/software directory on your staging host.

shell> cd /opt/continuent/software
shell> tar zxvf tungsten-operator-8.0.0-27.tar.gz

Docker Images​

The Tungsten Docker image file contains 3 individual tar files, one for each component of Tungsten Clustering.

Download the docker images file and unpack it within the /opt/continuent/software directory.

shell> cd /opt/continuent/software
shell> tar zxvf tungsten-clustering-docker-images-8.0.4-132-amd64.tar.gz

Load files into Docker Registry​

Now that all the files are downloaded, we need to load them into your local Docker daemon and push to the registry.

The examples below use the Intel (amd64) architecture files and commands applicable to loading into an AWS ECR Docker registry. Syntax may differ for other environments and should be adjusted accordingly.

shell> export ARCH=amd64
shell> export OP_RELEASE=8.0.0-27
shell> export CT_RELEASE=8.0.4-132
shell> export REGION=us-east-1
shell> export REGISTRY=111222333444.dkr.ecr.us-east-1.amazonaws.com

shell> cd /opt/continuent/software/tungsten-operator-${OP_RELEASE}
shell> docker load -i images/tungsten-operator-_${OP_RELEASE}-${ARCH}.tar

shell> cd /opt/continuent/software/tungsten-docker-images-${CT_RELEASE}
shell> docker load -i tungsten-connector-_${CT_RELEASE}-${ARCH}.tar
shell> docker load -i tungsten-manager-${CT_RELEASE}-${ARCH}.tar
shell> docker load -i tungsten-replicator-${CT_RELEASE}-${ARCH}.tar

Retrieve an authentication token and authenticate the Docker client to the ECR registry:

shell> aws ecr get-login-password --region ${REGION} | docker login --username AWS --password-stdin ${REGISTRY}

Tag the images:

shell> docker tag tungsten-operator:${OP_RELEASE} ${REGISTRY}/tungsten-operator:${OP_RELEASE}
shell> docker tag tungsten-connector:{CT_RELEASE} ${REGISTRY}/tungsten-connector:${CT_RELEASE}
shell> docker tag tungsten-manager:${CT_RELEASE} ${REGISTRY}/tungsten-manager:${CT_RELEASE}
shell> docker tag tungsten-replicator:${CT_RELEASE} ${REGISTRY}/tungsten-replicator:${CT_RELEASE}

Finally, push the images to the Docker Registry:

shell> docker push ${REGISTRY}/tungsten-operator:${OP_RELEASE}
shell> docker push ${REGISTRY}/tungsten-connector:${CT_RELEASE}
shell> docker push ${REGISTRY}/tungsten-manager:${CT_RELEASE}
shell> docker push ${REGISTRY}/tungsten-replicator:${CT_RELEASE}