> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/integrations/integrations-overview/docker-hub-integration.md).

# Docker Hub integration

Describes the functionality Release offers with its DockerHub integration

Release integrates with Docker Hub to allow you to pull images from private repositories.

![](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-6fb6a81b1f616e8ef6600177312cf3f7d85ecd46%2Fconnect-external-registries.png?alt=media)

Click on the **Connect Docker Hub Registry** button to view the integration form.

![Dockerhub integration form](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-8ecbc8ff74dd0b49e94f9a7af730d73835841555%2Fdockerhub.png?alt=media)

To use images stored in your Docker Hub account, add your Docker Hub username and password and create the integration.

Then set your image in your Application Template:

```
services:
- name: your-special-service
  image: yourdockerhubaccount/image:tag
```

The service `your-special-service` cannot have the `build` or `has_repo` keys. Those keys indicate that Release has built the image and Release will not attempt to pull the image from your Docker Hub repository.


---

# 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.release.com/integrations/integrations-overview/docker-hub-integration.md?ask=<question>&goal=<user_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.
