> 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/frequently-asked-questions/docker-support-faqs.md).

# Docker FAQ

### Do you support private Docker Hub images?

Yes, we support pulling images from a private repository in Docker Hub. Follow our [Docker Hub integration guide](/integrations/integrations-overview/docker-hub-integration.md) to link your Release account with your private registry to pull images during the build process.

### Do you support private (or public) Docker image repositories?

Yes, we support any Docker image repositories accessible on the internet or from within your own network (these must be reachable from the builders, which can be hosted in your own cluster). The [private registry integration](/integrations/integrations-overview/private-registry.md) can be configured to point to any host or registry reachable from the builders with basic authentication provided. You can even specify multiple registries by creating multiple integrations and refer to each registry by hostname in the `image:` section of your Application Template.

### Sometimes I get "Too Many Requests" when building or deploying.

```
429 Too Many Requests - Server message: toomanyrequests: You have reached your 
pull rate limit. You may increase the limit by authenticating and upgrading
```

If you see this error, you need to go to the **Integrations** tab and add your Docker Hub credentials to allow more pulls from Release. Unauthenticated requests to Docker Hub are limited and if your application is busy, you may need to upgrade to a paid Docker account to increase the number of builds allowed per hour.

### Where are the Docker images that Release builds hosted?

The build process pushes to an ECR (AWS) or Container Registry (GCP) in your account when `has_repo: true` and to a private repository integration if `has_repo: false` in your Application Template. If you have credentials to the account you can `docker login` to pull as usual. The SHA and registry address are available in the build logs or pod terminal.


---

# 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/frequently-asked-questions/docker-support-faqs.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.
