# Docker Registry

Docker Registry is the central repository of all Docker images .

User Account is the name of the organization account :

DNS name for Docker Registry is docker.io

Theese are publically accessible images that anyone can donwload and access but when we have applications builds inhouse that shouldn't be made available to public .

Hosting an internal Private Regittry maybe a good soltuion. Service provides like AWS, Azure & GCP provided Private Registry by default.

\>>What is if we running our application on-premise & don't have a private regitry . How do you deploy your own private registry within your organization . The Docker Registry is itself an another application & of-course available as a Docker Image.  The name os the image is **registry & it exposes the API on port 5000. Now we have our custom repository now how do we push image onto it. Using Docker image tag command to tag the image with a private registry URL in it & Since it is running on the same localhost we can use :**

**docker image tag my-image localhost:5000/my-image**

![](/files/-MERq_NDR1eEvjaICwCB)

![](/files/-MERtDT82nVo0CBI5Pj5)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://architectures.gitbook.io/project/docker/docker-registry.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.