Docker Registries

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

When building your application, you have the option to use the Replicated private registry, or any supported external private or public registry.

Replicated Registry

Every application created in Replicated has a private, completely isolated private Docker registry available. You can push images to your private registry by finding the endpoint at ( and using the Docker CLI to tag and push images. Replicated will automatically use the customer license file to authenticate and pull any images from the Replicated Registry.

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 page of the Replicated Vendor Portal.

An example of tagging an existing image is:

$ sudo docker tag worker

Logging In

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

$ sudo docker login
Username: [email protected]
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.

Using External Registries

Replicated supports pulling public, unauthenticated images from any Docker registry that supports the standard Docker Registry HTTP API.

Additionally, Replicated supports private images hosted in other registries including Docker Hub, and more.

To use private images from an external registry, you need to add the registry via the Vendor website. The guide for integrating a third party registry explains this in further detail.

Referencing Images from the Replicated Registry and Private Registries

Images stored in the Replicated private registry or an external private registry can be accessed by adding and configuring a static imagePullSecrets to any container definition that references the image.

Working with existing Docker Registries for Airgap Scenarios

Replicated Ship applications can be configured to work with a customer’s existing registry, in order to install into an airgap cluster. See this playbook for details.