1.0 Introduction
This article describes the steps to create image registries in the Fortanix Confidential Computing Manager (CCM). The users are provided the ability to quickly and easily navigate the interface to run containerized applications accordingly.
2.0 Setting Multiple Docker Registries
Fortanix Confidential Computing Manager allows you to add and save multiple docker registries in the Applications menu item.
Perform the following steps to add multiple docker registries:
In the CCM UI left navigation bar, click the Applications → Registries, and then click + ADD REGISTRY.
.png?sv=2022-11-02&spr=https&st=2026-03-21T03%3A37%3A58Z&se=2026-03-21T03%3A48%3A58Z&sr=c&sp=r&sig=S8H3tuLdFajCPMa%2B0Sq8NyfDDF8X7PGrU0fQ4ZZaHK8%3D)
Figure 1: Settings Page
The Registry Credentials are the credentials to access the private docker registry from which an image is going to be pulled or pushed.
On the Registry form:
Name: The name of the docker registry. The credentials will be used for every image with the same prefix. For example, docker.io.
Credentials: The username and password of the private docker registry.
.png?sv=2022-11-02&spr=https&st=2026-03-21T03%3A37%3A58Z&se=2026-03-21T03%3A48%3A58Z&sr=c&sp=r&sig=S8H3tuLdFajCPMa%2B0Sq8NyfDDF8X7PGrU0fQ4ZZaHK8%3D)
Figure 2: Enter Registry Credentials for Output Image
Click SAVE to add the docker registry credentials. After you save this, it is not required to provide the credentials for the docker image while creating an image.
The newly created registry credentials will appear in the Registries page table view.
.png?sv=2022-11-02&spr=https&st=2026-03-21T03%3A37%3A58Z&se=2026-03-21T03%3A48%3A58Z&sr=c&sp=r&sig=S8H3tuLdFajCPMa%2B0Sq8NyfDDF8X7PGrU0fQ4ZZaHK8%3D)
Figure 3: Registry Credential Table
2.1 Setting Multiple Azure Container Registries
In some cases, you might need to authenticate using the Azure container registry with az acr login in Azure CLI when the Docker daemon is not running in your environment. For example, you might need to run az acr login in a script in Azure Cloud Shell, which provides the Docker CLI but does not run the Docker daemon.
For this scenario:
Run
az acr loginfirst with the--expose-tokenparameter. This option exposes an access token instead of logging in through the Docker CLI.
Azure CLI:az acr login -name <acrName> --expose-tokenThe output displays the access token, abbreviated here:
{ “accessToken”: “eyjhbGci0iJSUzI1NiIs[...]24V7wA”, “loginServer”: “myregistry.azurecr.io” }Then, run docker login, passing
00000000-0000-0000-0000-000000000000as the username and using the access token as the password:Docker login myregistry.azurecr.io --username 00000000-0000-0000-0000-000000000000 --password eyjhbGci0iJSUzI1NiIs[...]24V7wAUse the Username ‘
00000000-0000-0000-0000-000000000000’ and access token as Password to configure the registry on Fortanix CCM..png?sv=2022-11-02&spr=https&st=2026-03-21T03%3A37%3A58Z&se=2026-03-21T03%3A48%3A58Z&sr=c&sp=r&sig=S8H3tuLdFajCPMa%2B0Sq8NyfDDF8X7PGrU0fQ4ZZaHK8%3D)
Figure 4: Configure Registry Credentials
When creating an image of an application in Fortanix CCM, we can use the Azure credentials saved in the Fortanix CCM Settings page.
(2).png?sv=2022-11-02&spr=https&st=2026-03-21T03%3A37%3A58Z&se=2026-03-21T03%3A48%3A58Z&sr=c&sp=r&sig=S8H3tuLdFajCPMa%2B0Sq8NyfDDF8X7PGrU0fQ4ZZaHK8%3D)
Figure 6: Use Saved Credentials for EOS Image Creation