Replicated Private Registry

How to push and access private images in Replicated's hosted private registry.

When building your application, you have the option of hosting your private images on the Replicated private registry or using external private and public registries.

Tagging Images

The first thing you will need to do is tag your image. Replicated accepts images in the standard Docker format:<application-slug>/<image-name>:<version>. You can find your application slug on the Images tab of the Replicated Vendor Portal.

An example of tagging an existing image is:

$ sudo docker tag myapp/worker

Logging In

Next you will need to log into the Replicated private registry with your Vendor account credentials. When prompted, you will use your email address for your username.

$ sudo docker login
Password: <your password>
Login Succeeded

Pushing Images

Finally you can push your image to the Replicated private registry.

$ sudo docker push
The push refers to a repository [] (len: 1)
Sending image list
Pushing repository (1 tags)
07595b42e5d5: Image successfully pushed
f9910c2fd14a: Image successfully pushed
4f409c5d1046: Image successfully pushed
8e471642d573: Image successfully pushed
Pushing tag for rev [8e471642d573] on {}

For additional information on building, tagging and pushing docker images, please refer to the Docker CLI Documentation.

Deploying to Kubernetes

When deploying an application to a Kubernetes cluster, Replicated will automatically deploy a secret named replicatedregistrykey. This secret can be used as an imagePullSecret to gain read-only access to the images from the on-prem environment.

For example:

       - name: frontend
       - name: replicatedregistrykey

Deploying to Swarm

When deploying an application to a swarm cluster, just reference the image in the Replicated registry. Replicated will automatically authenticate with the registry using the customer’s license.

For example:

version: '3.1'

      replicas: 1