Sync Images to Your Local Image Registry

Synchronize the images in your local image registry with their external source.

To avoid having stale images in your local repository, sync images on a daily basis.

Tanzu Mission Control publishes the list of artifacts without registry address. To pull images from Tanzu Mission Control, use the registry address that has been shared for your organization. Note that mirrored images can have a different base path, but the repository name and the image’s SHA256 checksum should be the same.

Prerequisites

Log in with the tanzu CLI.

Make sure you have the appropriate permissions to sync images.

• To sync images you must be associated with the cluster.admin role in TMC.

Procedure

1. List the images using the tanzu CLI.

   tanzu mission-control agentartifacts list

   The output looks something like this:

   harbor.tanzu.io:8443/tmc/498533941640.dkr.ecr.us-west-2.amazonaws.com/extensions/gatekeeper@sha256:8ac9ccca5491e7988d4f310cc1f89361a1522357321487a69d8a8baa4eac7bb4
   harbor.tanzu.io:8443/tmc/498533941640.dkr.ecr.us-west-2.amazonaws.com/extensions/gatekeeper-operator@sha256:00766a996825792e35fe30dd678605e698a10cafdd343bbb56cc973a1749afed
   harbor.tanzu.io:8443/tmc/498533941640.dkr.ecr.us-west-2.amazonaws.com/extensions/build-integrations-images/kapp-controller-v0-51-0@sha256:c6db8d0a2322fee1aa30940fd84ee11aca4e3b54ae39bffc43e34dda502919d9
   harbor.tanzu.io:8443/tmc/498533941640.dkr.ecr.us-west-2.amazonaws.com/extensions/build-integrations/package-deployment@sha256:5e257b47fd350de3e2425e9be2b7b918e29d7098f693873e569a8895bfc845f2
   harbor.tanzu.io:8443/tmc/498533941640.dkr.ecr.us-west-2.amazonaws.com/extensions/agent-updater/agent-updater@sha256:f812fa11c991442515dc1ad587dc0fd52e1b081114d7d76b129c13f6d733309e
   harbor.tanzu.io:8443/tmc/498533941640.dkr.ecr.us-west-2.amazonaws.com/extensions/agent-updater/agentupdater-workload@sha256:d6f8a0d12158152a6a839e0900d83e760a16629a6b1e753667276d56abbf7d14 
   

2. Copy, re-tag, and push the images.
   For each artifact in the list, you must pull the artifact, re-tag it, and then push it.
   The following example uses docker commands to do this for the agent-updater artifact.

   docker pull harbor.tanzu.io:8443/tmc/498533941640.dkr.ecr.us-west-2.amazonaws.com/extensions/agent-updater/agent-updater@sha256:f812fa11c991442515dc1ad587dc0fd52e1b081114d7d76b129c13f6d733309e

   docker tag harbor.tanzu.io:8443/tmc/498533941640.dkr.ecr.us-west-2.amazonaws.com/extensions/agent-updater/agent-updater@sha256:f812fa11c991442515dc1ad587dc0fd52e1b081114d7d76b129c13f6d733309e lir.tanzu.io:8443/lir/extensions/agent-updater

   docker push lir.tanzu.io:8443/lir/extensions/agent-updater

3. Copy the Tanzu Standard package repository.
   For the Carvel catalog feature, the Tanzu Standard package repository must be copied to the local registry. Use the steps provided in Copying Tanzu Standard and Inspection Images in Installing and Running VMware Tanzu Mission Control Self-Managed.