Skip to content

Commit cd6b6e6

Browse files
hub: usage refresh (#21782)
<!--Delete sections as needed --> ## Description Refreshed the usage and limits topic for Docker Hub. https://deploy-preview-21782--docsdocker.netlify.app/docker-hub/usage/ https://deploy-preview-21782--docsdocker.netlify.app/docker-hub/usage/pulls/ https://deploy-preview-21782--docsdocker.netlify.app/docker-hub/usage/storage/ https://deploy-preview-21782--docsdocker.netlify.app/docker-hub/usage/manage/ ## Related issues or tickets ENGDOCS-2361 ## Reviews <!-- Notes for reviewers here --> <!-- List applicable reviews (optionally @tag reviewers) --> - [ ] Editorial review --------- Signed-off-by: Craig <[email protected]> Co-authored-by: Allie Sadler <[email protected]>
1 parent 2c8d8f2 commit cd6b6e6

File tree

11 files changed

+358
-389
lines changed

11 files changed

+358
-389
lines changed

content/manuals/desktop/setup/sign-in.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ In large enterprises where admin access is restricted, administrators can [enfor
4242

4343
- You can access your Docker Hub repositories directly from Docker Desktop.
4444

45-
- Authenticated users also get a higher pull rate limit compared to anonymous users. For example, if you are authenticated, you get 200 pulls per 6 hour period, compared to 100 pulls per 6 hour period per IP address for anonymous users. For more information, see [Download rate limit](/manuals/docker-hub/download-rate-limit.md).
45+
- Authenticated users also get a higher pull rate limit compared to anonymous users. For more information, see [Usage and limits](/manuals/docker-hub/usage/_index.md).
4646

4747
- Improve your organization’s security posture for containerized development by taking advantage of [Hardened Desktop](/manuals/security/for-admins/hardened-desktop/_index.md).
4848

content/manuals/docker-hub/_index.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,10 @@ grid:
2424
description: Learn about organization administration.
2525
icon: store
2626
link: /admin/
27-
- title: Usage
27+
- title: Usage and limits
2828
description: Explore usage limits and how to better utilize Docker Hub.
2929
icon: leaderboard
30-
link: /docker-hub/download-rate-limit/
30+
link: /docker-hub/usage/
3131
- title: Release notes
3232
description: Find out about new features, improvements, and bug fixes.
3333
icon: note_add

content/manuals/docker-hub/download-rate-limit.md

-381
This file was deleted.

content/manuals/docker-hub/image-library/mirror.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Hub can be mirrored.
3838

3939
> [!NOTE]
4040
>
41-
> Mirrors of Docker Hub are still subject to Docker's [fair use policy](/manuals/docker-hub/download-rate-limit.md#fair-use).
41+
> Mirrors of Docker Hub are still subject to Docker's [fair use policy](/manuals/docker-hub/usage/_index.md#fair-use).
4242
4343
### Solution
4444

content/manuals/docker-hub/release-notes.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -199,7 +199,7 @@ Docker introduces Hub Vulnerability Scanning which enables you to automatically
199199

200200
* Docker has announced a new, per-seat pricing model to accelerate developer workflows for cloud-native development. The previous private repository/concurrent autobuild-based plans have been replaced with new **Pro** and **Team** plans that include unlimited private repositories. For more information, see [Docker subscription](../subscription/_index.md).
201201

202-
* Docker has enabled download rate limits for downloads and pull requests on Docker Hub. This caps the number of objects that users can download within a specified timeframe. For more information, see [Download rate limit](download-rate-limit.md).
202+
* Docker has enabled download rate limits for downloads and pull requests on Docker Hub. This caps the number of objects that users can download within a specified timeframe. For more information, see [Usage and limits](/manuals/docker-hub/usage/_index.md).
203203

204204
## 2019-11-04
205205

+56
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
---
2+
description: Learn about usage and limits for Docker Hub.
3+
keywords: Docker Hub, limit, usage
4+
title: Docker Hub usage and limits
5+
linkTitle: Usage and limits
6+
weight: 30
7+
aliases:
8+
/docker-hub/download-rate-limit/
9+
---
10+
11+
{{< include "hub-limits.md" >}}
12+
13+
When using Docker Hub, unauthenticated and Docker Personal users are subject to
14+
strict limits. In contrast, Docker Pro, Team, and Business users benefit from a
15+
consumption-based model with a base amount of included usage. This included
16+
usage is not a hard limit; users can scale or upgrade their subscriptions to
17+
receive additional usage or use on-demand usage.
18+
19+
The following table provides an overview of the included usage and limits for each
20+
user type, subject to fair use:
21+
22+
23+
| User type | Pulls per month | Pull rate limit per hour | Public repositories | Public repository storage | Private repositories | Private repository storage |
24+
|--------------------------|-----------------|--------------------------|---------------------|---------------------------|----------------------|----------------------------|
25+
| Business (authenticated) | 1M | Unlimited | Unlimited | Unlimited | Unlimited | Up to 500 GB |
26+
| Team (authenticated) | 100K | Unlimited | Unlimited | Unlimited | Unlimited | Up to 50 GB |
27+
| Pro (authenticated) | 25K | Unlimited | Unlimited | Unlimited | Unlimited | Up to 5 GB |
28+
| Personal (authenticated) | Not applicable | 40 | Unlimited | Unlimited | Up to 1 | Up to 2 GB |
29+
| Unauthenticated users | Not applicable | 10 per IP address | Not applicable | Not applicable | Not applicable | Not applicable |
30+
31+
For more details, see the following:
32+
33+
- [Pull usage and limits](./pulls.md)
34+
- [Storage usage and limits](./storage.md)
35+
36+
## Fair use
37+
38+
When utilizing the Docker Platform, users should be aware that excessive data
39+
transfer, pull rates, or data storage can lead to throttling, or additional
40+
charges. To ensure fair resource usage and maintain service quality, we reserve
41+
the right to impose restrictions or apply additional charges to accounts
42+
exhibiting excessive data and storage consumption.
43+
44+
### Abuse rate limit
45+
46+
Docker Hub has an abuse rate limit to protect the application and
47+
infrastructure. This limit applies to all requests to Hub properties including
48+
web pages, APIs, and image pulls. The limit is applied per-IP, and while the
49+
limit changes over time depending on load and other factors, it's in the order
50+
of thousands of requests per minute. The abuse limit applies to all users
51+
equally regardless of account level.
52+
53+
You can differentiate between the pull rate limit and abuse rate limit by
54+
looking at the error code. The abuse limit returns a simple `429 Too Many
55+
Requests` response. The pull limit returns a longer error message that includes
56+
a link to documentation.
+49
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
---
2+
description: Learn how to optimize and manage your Docker Hub usage.
3+
keywords: Docker Hub, limit, usage
4+
title: Best practices for optimizing Docker Hub usage
5+
linkTitle: Optimize usage
6+
weight: 40
7+
---
8+
9+
Use the following steps to help optimize and manage your Docker Hub usage for
10+
both individuals and organizations:
11+
12+
1. [View your Docker Hub usage](https://hub.docker.com/usage).
13+
14+
2. Use the Docker Hub usage data to identify which accounts consume the most
15+
data, determine peak usage times, and identify which images are related to
16+
the most data usage. In addition, look for usage trends, such as the
17+
following:
18+
19+
- Inefficient pull behavior: Identify frequently accessed repositories to
20+
assess whether you can optimize caching practices or consolidate usage to
21+
reduce pulls.
22+
- Inefficient automated systems: Check which automated tools, such as CI/CD
23+
pipelines, may be causing higher pull rates, and configure them to avoid
24+
unnecessary image pulls.
25+
26+
3. Optimize image pulls by:
27+
28+
- Using caching: Implement local image caching via
29+
[mirroring](/docker-hub/mirror/) or within your CI/CD pipelines to reduce
30+
redundant pulls.
31+
- Automating manual workflows: Avoid unnecessary pulls by configuring automated
32+
systems to pull only when a new version of an image is available.
33+
34+
4. Optimize your storage by:
35+
36+
- Regularly auditing and removing repositories with untagged, unused, or outdated images.
37+
- Looking for private repositories in Hub storage that exceed your plan's limits.
38+
39+
5. Increase your limits by upgrading or purchasing additional consumption. For
40+
details, see [Scale your subscription](/manuals/subscription/scale.md).
41+
42+
6. For organizations, monitor and enforce organizational policies by doing the
43+
following:
44+
45+
- Routinely [view Docker Hub usage](https://hub.docker.com/usage) to monitor usage.
46+
- [Enforce sign-in](/security/for-admins/enforce-sign-in/) to ensure that you
47+
can monitor the usage of your users and users receive higher usage limits.
48+
- Look for duplicate user accounts in Docker and remove accounts from your organization
49+
as needed.

0 commit comments

Comments
 (0)