SAS Viya Administration - Mirror registry setup
To set up the mirror registry on Azure, make sure you have the mirrormgr binaries downloaded, and that the server / workstation where you are running the command from has at least 150 GB of free space. This is necessary to ensure that the mirrormgr command has ample space to store the Docker images that it pulls from SAS before it uploads them to your mirror registry.
First you need to fetch an authentication token for your private Docker registry (ideally should be a hosted one, like ACR on Azure or ECR on Amazon):
az login (follow the instructions on the screen to authenticate to azure)
az acr login --name <registry_name> --expose-tokenRetrieve the token generated by the previous command. Output should look something like this:
{
"accessToken": "token-contents",
"loginServer": "mirrormgr.azurecr.io"
}Then, make sure that the folder where you are running the command from contains the following files which you have previously downloaded from SAS:
- the deployment assets archive (*.tgz)
- the certs archive (*-certs.zip)
Finally, run the following command to copy the docker images to your registry, while ensuring that their version matches the cadence and release specified in the deployment manifests:
./mirrormgr mirror registry --deployment-data <certs zip> --deployment-assets <deployment assets tgz archive> --destination <mirror registry hostname> --username 00000000-0000-0000-0000-000000000000 --password <access token retrieved previously>The --deployment-assets command will ensure that the mirrormgr utility will scan the deployment manifests and ensure that it only uploads the necessary versions of the docker images to your docker registry.
!! Important: Do not use the '--latest' flag unless you specifically want the latest versions of the images uploaded. Chances are that the manifests you are using to deploy Viya don't reference the newest version, so you might get a mismatch. Alternatively, you could use the '--cadence' flag to target a specific release