-
Notifications
You must be signed in to change notification settings - Fork 7.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Showing
11 changed files
with
358 additions
and
389 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
--- | ||
description: Learn about usage and limits for Docker Hub. | ||
keywords: Docker Hub, limit, usage | ||
title: Docker Hub usage and limits | ||
linkTitle: Usage and limits | ||
weight: 30 | ||
aliases: | ||
/docker-hub/download-rate-limit/ | ||
--- | ||
|
||
{{< include "hub-limits.md" >}} | ||
|
||
When using Docker Hub, unauthenticated and Docker Personal users are subject to | ||
strict limits. In contrast, Docker Pro, Team, and Business users benefit from a | ||
consumption-based model with a base amount of included usage. This included | ||
usage is not a hard limit; users can scale or upgrade their subscriptions to | ||
receive additional usage or use on-demand usage. | ||
|
||
The following table provides an overview of the included usage and limits for each | ||
user type, subject to fair use: | ||
|
||
|
||
| User type | Pulls per month | Pull rate limit per hour | Public repositories | Public repository storage | Private repositories | Private repository storage | | ||
|--------------------------|-----------------|--------------------------|---------------------|---------------------------|----------------------|----------------------------| | ||
| Business (authenticated) | 1M | Unlimited | Unlimited | Unlimited | Unlimited | Up to 500 GB | | ||
| Team (authenticated) | 100K | Unlimited | Unlimited | Unlimited | Unlimited | Up to 50 GB | | ||
| Pro (authenticated) | 25K | Unlimited | Unlimited | Unlimited | Unlimited | Up to 5 GB | | ||
| Personal (authenticated) | Not applicable | 40 | Unlimited | Unlimited | Up to 1 | Up to 2 GB | | ||
| Unauthenticated users | Not applicable | 10 per IP address | Not applicable | Not applicable | Not applicable | Not applicable | | ||
|
||
For more details, see the following: | ||
|
||
- [Pull usage and limits](./pulls.md) | ||
- [Storage usage and limits](./storage.md) | ||
|
||
## Fair use | ||
|
||
When utilizing the Docker Platform, users should be aware that excessive data | ||
transfer, pull rates, or data storage can lead to throttling, or additional | ||
charges. To ensure fair resource usage and maintain service quality, we reserve | ||
Check warning on line 40 in content/manuals/docker-hub/usage/_index.md GitHub Actions / vale
|
||
the right to impose restrictions or apply additional charges to accounts | ||
exhibiting excessive data and storage consumption. | ||
|
||
### Abuse rate limit | ||
|
||
Docker Hub has an abuse rate limit to protect the application and | ||
infrastructure. This limit applies to all requests to Hub properties including | ||
web pages, APIs, and image pulls. The limit is applied per-IP, and while the | ||
limit changes over time depending on load and other factors, it's in the order | ||
of thousands of requests per minute. The abuse limit applies to all users | ||
equally regardless of account level. | ||
|
||
You can differentiate between the pull rate limit and abuse rate limit by | ||
looking at the error code. The abuse limit returns a simple `429 Too Many | ||
Requests` response. The pull limit returns a longer error message that includes | ||
a link to documentation. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
--- | ||
description: Learn how to optimize and manage your Docker Hub usage. | ||
keywords: Docker Hub, limit, usage | ||
title: Best practices for optimizing Docker Hub usage | ||
linkTitle: Optimize usage | ||
weight: 40 | ||
--- | ||
|
||
Use the following steps to help optimize and manage your Docker Hub usage for | ||
both individuals and organizations: | ||
|
||
1. [View your Docker Hub usage](https://hub.docker.com/usage). | ||
|
||
2. Use the Docker Hub usage data to identify which accounts consume the most | ||
data, determine peak usage times, and identify which images are related to | ||
the most data usage. In addition, look for usage trends, such as the | ||
following: | ||
|
||
- Inefficient pull behavior: Identify frequently accessed repositories to | ||
assess whether you can optimize caching practices or consolidate usage to | ||
reduce pulls. | ||
- Inefficient automated systems: Check which automated tools, such as CI/CD | ||
Check warning on line 22 in content/manuals/docker-hub/usage/manage.md GitHub Actions / vale
|
||
pipelines, may be causing higher pull rates, and configure them to avoid | ||
unnecessary image pulls. | ||
|
||
3. Optimize image pulls by: | ||
|
||
- Use caching: Implement local image caching via | ||
[mirroring](/docker-hub/mirror/) or within your CI/CD pipelines to reduce | ||
Check warning on line 29 in content/manuals/docker-hub/usage/manage.md GitHub Actions / vale
|
||
redundant pulls. | ||
- Automate manual workflows: Avoid unnecessary pulls by configuring automated | ||
systems to pull only when a new version of an image is available. | ||
|
||
4. Optimize your storage by: | ||
|
||
- Regularly audit and remove repositories with untagged, unused, or outdated images. | ||
- Look for private repositories in Hub storage that exceed your plan's limits. | ||
|
||
5. Increase your limits by upgrading or purchasing additional consumption. For | ||
details, see [Scale your subscription](/manuals/subscription/scale.md). | ||
|
||
6. For organizations, monitor and enforce organizational policies by doing the | ||
following: | ||
|
||
- Routinely [view Docker Hub usage](https://hub.docker.com/usage) to monitor usage. | ||
- [Enforce sign-in](/security/for-admins/enforce-sign-in/) to ensure that you | ||
can monitor the usage of your users and users receive higher usage limits. | ||
- Look for duplicate user accounts in Docker and remove accounts from your organization | ||
as needed. |
Oops, something went wrong.