Skip to content

Commit 036518f

Browse files
dvdksnDocker Docs Agent
dvdksn
and
Docker Docs Agent
authored
docs: update broken CircleCI link to current path (#24457)
## Summary - Updates the CircleCI link in the "Third-party platforms" section of `content/manuals/docker-hub/usage/pulls.md` - Removes the `/2.0/` versioned path segment that CircleCI dropped when they reorganized their documentation structure - The old URL (`circleci.com/docs/2.0/private-images/`) returns 404; the updated URL (`circleci.com/docs/private-images/`) follows CircleCI's current unversioned path pattern Closes #24438 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Docker Docs Agent <agent@docker-docs-harness.local>
1 parent dfa8f0f commit 036518f

1 file changed

Lines changed: 25 additions & 29 deletions

File tree

  • content/manuals/docker-hub/usage

‎content/manuals/docker-hub/usage/pulls.md‎

Lines changed: 25 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ The following pull usage and limits apply based on your subscription, subject to
1717
fair use:
1818

1919
| User type | Pull rate limit per 6 hours |
20-
|--------------------------|-----------------------------------------|
20+
| ------------------------ | --------------------------------------- |
2121
| Business (authenticated) | Unlimited |
2222
| Team (authenticated) | Unlimited |
2323
| Pro (authenticated) | Unlimited |
@@ -28,15 +28,15 @@ fair use:
2828

2929
A pull is defined as the following:
3030

31-
- A Docker pull includes both a version check and any download that
32-
occurs as a result of the pull. Depending on the client, a `docker pull` can
33-
verify the existence of an image or tag without downloading it by performing
34-
a version check.
35-
- Version checks do not count towards usage pricing.
36-
- A pull for a normal image makes one pull for a [single
37-
manifest](https://github.com/opencontainers/image-spec/blob/main/manifest.md).
38-
- A pull for a multi-arch image will count as one pull for each
39-
different architecture.
31+
- A Docker pull includes both a version check and any download that
32+
occurs as a result of the pull. Depending on the client, a `docker pull` can
33+
verify the existence of an image or tag without downloading it by performing
34+
a version check.
35+
- Version checks do not count towards usage pricing.
36+
- A pull for a normal image makes one pull for a [single
37+
manifest](https://github.com/opencontainers/image-spec/blob/main/manifest.md).
38+
- A pull for a multi-arch image will count as one pull for each
39+
different architecture.
4040

4141
## Pull attribution
4242

@@ -53,17 +53,16 @@ Attribution is based on the following:
5353
verified domain, the attribution is set to be the owner of that
5454
[domain](/manuals/enterprise/security/single-sign-on/faqs/domain-faqs.md).
5555
- Single organization membership:
56-
- If the owner of the verified domain is a company and the user is part of
57-
only one organization within that
58-
[company](../../admin/faqs/company-faqs.md#what-features-are-supported-at-the-company-level),
59-
the pull is attributed to that specific organization.
60-
- If the user is part of only one organization, the pull is attributed to
61-
that specific organization.
56+
- If the owner of the verified domain is a company and the user is part of
57+
only one organization within that
58+
[company](../../admin/faqs/company-faqs.md#what-features-are-supported-at-the-company-level),
59+
the pull is attributed to that specific organization.
60+
- If the user is part of only one organization, the pull is attributed to
61+
that specific organization.
6262
- Multiple organization memberships: If the user is part of multiple
6363
organizations under the company, the pull is attributed to the user's personal
6464
namespace.
6565

66-
6766
### Authentication
6867

6968
To ensure correct attribution of your pulls, you must authenticate with Docker
@@ -122,7 +121,7 @@ If you're using any third-party platforms, follow your provider’s instructions
122121
- [AWS ECS/Fargate](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/private-auth.html)
123122
- [Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/library/service-endpoints?view=azure-devops&tabs=yaml#sep-docreg)
124123
- [Chipper CI](https://docs.chipperci.com/builds/docker/#rate-limit-auth)
125-
- [CircleCI](https://circleci.com/docs/2.0/private-images/)
124+
- [CircleCI](https://circleci.com/docs/guides/execution-managed/private-images/)
126125
- [Codefresh](https://codefresh.io/docs/docs/docker-registries/external-docker-registries/docker-hub/)
127126
- [Drone.io](https://docs.drone.io/pipeline/docker/syntax/images/#pulling-private-images)
128127
- [GitLab](https://docs.gitlab.com/ee/user/packages/container_registry/#authenticate-with-the-container-registry)
@@ -137,7 +136,7 @@ On that page, you can also send a report to your email that contains a comma
137136
separated file with the following detailed information.
138137

139138
| CSV column | Definition | Usage guidance |
140-
|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
139+
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
141140
| `datehour` | The date and hour (`yyyy/mm/dd/hh`) of the pull that resulted in the data transfer. | This helps in identifying peak usage times and patterns. |
142141
| `user_name` | The Docker ID of the user that pulled the image | This lets organization owners track data consumption per user and manage resources effectively. |
143142
| `repository` | The name of the repository of the image that was pulled. | This lets you identify which repositories are most frequently accessed and consume most of the data transfer. |
@@ -147,7 +146,7 @@ separated file with the following detailed information.
147146
| `tag` | The tag for the image. The tag is only available if the pull included a tag. | This helps in identifying the image. Tags are often used to identify specific versions or variants of an image. |
148147
| `digest` | The unique image digest for the image. | This helps in identifying the image. |
149148
| `version_checks` | The number of version checks accumulated for the date and hour of each image repository. Depending on the client, a pull can do a version check to verify the existence of an image or tag without downloading it. | This helps identify the frequency of version checks, which you can use to analyze usage trends and potential unexpected behaviors. |
150-
| `pulls` | The number of pulls accumulated for the date and hour of each image repository. | This helps identify the frequency of repository pulls, which you can use to analyze usage trends and potential unexpected behaviors. |
149+
| `pulls` | The number of pulls accumulated for the date and hour of each image repository. | This helps identify the frequency of repository pulls, which you can use to analyze usage trends and potential unexpected behaviors. |
151150

152151
## View pull rate and limit
153152

@@ -172,25 +171,23 @@ To view your current pull rate and limit:
172171
> To check your limits, you need `curl`, `grep`, and `jq` installed.
173172
174173
1. Get a token.
175-
176174
- To get a token anonymously, if you are pulling anonymously:
177175

178-
```console
179-
$ TOKEN=$(curl "https://auth.docker.io/token?service=registry.docker.io&scope=repository:ratelimitpreview/test:pull" | jq -r .token)
180-
```
176+
```console
177+
$ TOKEN=$(curl "https://auth.docker.io/token?service=registry.docker.io&scope=repository:ratelimitpreview/test:pull" | jq -r .token)
178+
```
181179

182180
- To get a token with a user account, if you are authenticated, insert your
183181
username and password in the following command:
184182

185-
```console
186-
$ TOKEN=$(curl --user 'username:password' "https://auth.docker.io/token?service=registry.docker.io&scope=repository:ratelimitpreview/test:pull" | jq -r .token)
187-
```
183+
```console
184+
$ TOKEN=$(curl --user 'username:password' "https://auth.docker.io/token?service=registry.docker.io&scope=repository:ratelimitpreview/test:pull" | jq -r .token)
185+
```
188186

189187
2. Get the headers that contain your limits. These headers are returned on both
190188
GET and HEAD requests. Using GET emulates a real pull and counts towards the
191189
limit. Using HEAD won't.
192190

193-
194191
```console
195192
$ curl --head -H "Authorization: Bearer $TOKEN" https://registry-1.docker.io/v2/ratelimitpreview/test/manifests/latest
196193
```
@@ -211,4 +208,3 @@ To view your current pull rate and limit:
211208
organization. It could also mean that the user you are pulling as is part of a
212209
paid Docker subscription. Pulling that image won't count toward pull rate limits if you
213210
don't see these headers.
214-

0 commit comments

Comments
 (0)