---
title: "Application Build Registry"
slug: "fortanix-ccm-application-build-registry"
updated: 2026-07-22T13:46:30Z
published: 2026-07-22T13:46:30Z
canonical: "support.fortanix.com/fortanix-ccm-application-build-registry"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.fortanix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Application Build Registry

## 1.0 Introduction

This article describes how to configure image registries in Fortanix Confidential Computing Manager (CCM). Configuring registries allows users to securely store and access container images required for deploying containerized applications.

## 2.0 Configure Multiple Docker Registries

Fortanix CCM allows users to add and manage multiple Docker registries from the **Applications** page.

Perform the following steps to add multiple docker registries:

1. In the CCM user interface (UI) left navigation panel, click **Applications** → **REGISTERIES**, and then click **ADD REGISTRY**.

![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/fortanix-confidential-computing-manager-image-registry-user-guide-v3.0-image-d434ccob.png)

**Figure 1: Add registry**

Registry credentials are used to authenticate access to the private Docker registry from which container images are pulled or pushed.
2. In the **Add Registry** form:
  1. **Registry Name:** The name of the Docker registry. The credentials will be used for every image with the same prefix. For example, **docker.io**.
  2. **Credentials** and **Password:** The username and password used to authenticate with the private Docker registry.
3. Click **ADD REGISTRY** to add the docker registry credentials.

Once the registry credentials are saved, users are not required to enter the Docker registry credentials again while creating an application image.

The newly added registry credentials appear in the **REGISTRIES** table.

## 3.0 Configure Multiple Azure Container Registries

In some environments where the Docker daemon is not running, Azure Container Registry authentication can be performed using the `az acr login` command in Azure CLI.

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 such scenario:

1. Run `az acr` login first with the `--expose-token` parameter.
2. Run the `az acr` login command with the `--expose-token` parameter. This option exposes an access token instead of logging in through the Docker CLI.

Azure CLI:

```bash
az acr login -name <acrName> --expose-token
```

The output displays the access token, abbreviated here:

```bash
{
“accessToken”: “eyjhbGci0iJSUzI1NiIs[...]24V7wA”,
“loginServer”: “myregistry.azurecr.io”
}
```
3. Then, run docker login, using `00000000-0000-0000-0000-000000000000` as the username and the access token as the password:

```bash
Docker login myregistry.azurecr.io --username 00000000-0000-0000-0000-000000000000 --password eyjhbGci0iJSUzI1NiIs[...]24V7wA
```

Use `00000000-0000-0000-0000-000000000000` as the username and the access token as the password while configuring the registry in Fortanix CCM.

![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/fortanix-confidential-computing-manager-image-registry-user-guide-v3.0-image-87e9844o.png)

**Figure 2: Configure registry credentials**

When creating an application build in Fortanix CCM, users can use the Azure registry credentials saved in the Fortanix CCM **Settings** page.

## Related

- [Domain and Application Build Approval](/fortanix-ccm-domain-and-application-build-approval.md)
- [How does Fortanix DSM SaaS Work?](/how-does-fortanix-dsm-saas-work.md)
- [Logging](/fortanix-dsm-logging.md)
- [Create Application Build](/fortanix-ccm-create-application-build.md)