Skip to main content

Connecting to an Image Registry

When packaging and delivering an application with Replicated, you can include private images for the application without distributing registry credentials to your customer.

The customer license file can grant revokable image pull access to private images, whether the images are stored in the Replicated private registry or a supported external registry:

About Connecting to an External Registry

If your application images are available in a private image registry exposed to the Internet, such as Docker Hub,, Amazon Elastic Container Registry (ECR), Google Container Registry (GCR), or Artifactory, then the customer licenses for your application can grant proxy, or pull-through, access to the assignee without exposing registry credentials to the customer.

With proxy access, the app manager can use the Replicated registry proxy service to pull private images from an external registry. Instances of your application can then pull private images from the proxy service at during deployment. The app manager determines what images are private by attempting to fetch image metadata. If the request is forbidden, the app manager pulls the image through instead of pulling the image directly from an external registry.

Connecting the app manager to your external registry through a proxy is useful and recommended because it prevents you from having to modify the process you use to build and push application images in order to deploy your application with Replicated.

It also allows you to revoke a customer’s ability to pull private images without having to manage image access through separate identity or authentication systems. For example, when you connect the app manager to your external image registry, a customer's ability to pull private images is revoked when their trial license expires.

To grant proxy access to your external registry, see Configure Access to an External Registry below.

The following diagram demonstrates how the registry proxy service pulls images from your external registry, and how deployed instances of your application pull images from the proxy service:

Registry proxy service workflow diagram

View a larger version of this image

For more information about how the app manager uses the registry proxy service, see How the App Manager Accesses Private Images below.

Configure Access to an External Registry

You can provide the credentials for an external registry in the vendor portal to grant the app manager proxy access to the private application images in the registry.

All applications in your vendor portal Team have access to the external registry that you add. This means that you can use the images in the external registry across multiple apps in the Team.

To follow a tutorial connecting a sample app to an Amazon Elastic Container Registry (ECR), see Tutorial: Using ECR for Private Images.

To configure access to your private images in an external registry:

  1. Log in to the vendor portal and go to the Images page.

  2. Click Add external registry.

    Add External Registry dialog in the vendor portal

  3. Click the Other Registry or DockerHub tab.

  4. Complete the fields in the dialog:

    EndpointEnter the endpoint, such as,, or
    Username and PasswordProvide the username and password for an account that has pull access to the private registry.

    For Amazon ECR registries, provide the Access Key ID and Secret Key for a Service Account User that has pull access to the registry. See Setting up the Service Account User.

    Replicated stores your username and password encrypted and securely. Your credentials and the encryption key do not leave Replicated servers.

Push Images to the Replicated Private Registry

You can host the private images for your application on the Replicated private registry. Hosting your images on the Replicated private registry is useful if you do not already have your images in an existing private registry. It is also useful for testing purposes.

For more information about building, tagging, and pushing Docker images, see the Docker CLI documentation.

To push images to the Replicated private registry:

  1. Do one of the following to connect with the container registry:

    • (Recommended) Log in with a user token: Use docker login with your vendor portal email as the username and a vendor portal user token as the password. For more information, see User tokens in Using Vendor API tokens.
    • Log in with a service account or team token: Use docker login with a Replicated vendor portal service account or team token as the password. You can use any string as the username. For more information, see Service accounts and Team tokens in Using Vendor API tokens.
    • Log in with your credentials: Use docker login with your vendor portal email and password as the credentials.
  2. Tag your private image with the Replicated registry hostname in the standard Docker format:

    docker tag IMAGE_NAME


    • IMAGE_NAME is the name of the existing private image for your application.

    • APPLICATION_SLUG is the slug assigned to your application. You can find your application slug on the Images page of the vendor portal.

    • TARGET_IMAGE_NAME is a name for the image. Replicated recommends that the TARGET_IMAGE_NAME is the same as the IMAGE_NAME.

    • TAG is a tag for the image.

      For example:

      $ docker tag worker
  3. Push your private image to the Replicated private registry:

    $ docker push

How the App Manager Accesses Private Images

The app manager uses Kustomize to change the location of the private image registry in the PodSpec during application deployment from the external registry domain to the Replicated proxy service domain. It then creates an imagePullSecret to access the images through the proxy service.

Patching the Image Location with Kustomize

When the app manager is installing an application, it attempts to load image manifests using the image reference from the PodSpec. If the app manager receives a 401 response, it assumes that this is a private image that must be proxied through the registry proxy service.

The app manager uses Kustomize to patch the midstream/kustomization.yaml file to change the image name during deployment to reference the proxy service.

For example, a PodSpec for a Deployment references a private image hosted at

  apiVersion: apps/v1
kind: Deployment
name: example
- name: api

When this application is deployed, the app manager detects that it cannot access the image at So, it creates a patch in the midstream/kustomization.yaml file that changes the image name in all manifest files for the application:

- ../../base
- name:

This causes the container runtime in the cluster to use the proxy service to pull the images, using the license information provided to the app manager for authentication.

Accessing the Proxy Service with an Image Pull Secret

During installation, the app manager automatically creates an imagePullSecret that is based on the customer license. The app manager uses this secret to authenticate and pull private images from

The app manager does not patch the image location URL for images hosted on the Replicated private registry at However, the app manager adds the same imagePullSecret to PodSpecs that reference images in the Replicated private registry.


When deploying Pods to namespaces other than the app manager application namespace, you must add the namespace to the additionalNamespaces attribute of the Application custom resource manifest. This ensures the app manager can provision the imagePullSecret in the namespace to allow the Pod to pull the image. For more information about the additionalNamespaces attribute, see Defining Additional Namespaces.

Support for Image Tags and Digests

The app manager supports image tags for applications in all use cases.

The app manager supports image digests only for online (Internet-connected) installations. You can also use image tags and digests together for online installations. Image digests are not supported for air gap installations.

Tutoiral: Using ECR for Private Images