> For the complete documentation index, see [llms.txt](https://docs.connect.jfrog.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.connect.jfrog.io/administration-new-ui/general-settings/registry/add-private-docker.md).
# Add Private Docker
Use JFrog Connect to link a Docker registry and deploy updates directly from your container registry to the edge devices.
When you use Docker step types in a software update, you can configure the flow step to pull container images directly from your Docker Hub registry. All you need to do is link your Docker Hub registry to your JFrog Connect account. You can also link a Docker registry from other registry providers, such as AWS ECR or other private registries.
To connect a private (non-JFrog) Docker registry, do the following:
1. In **General** **Settings**, go to **Registry Management** and click the **Private Docker** tab.
2. Click **Add Registry** on the upper right and select a **Registry Provider** from the dropdown (AWS ECR, DockerHub, or a Private provider).
3. Complete the configuration information for the registry provider you selected and confirm. The information required for each provider is different. The example below is for adding DockerHub as the registry provider.
## What’s Next?
Learn how to [delete a link to a private Docker registry](/administration-new-ui/general-settings/registry/add-private-docker/delete-private-docker.md).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.connect.jfrog.io/administration-new-ui/general-settings/registry/add-private-docker.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
