Skip to content

Commit 2926b46

Browse files
authored
Clarify title and description (#24)
1 parent 7942dc2 commit 2926b46

File tree

1 file changed

+2
-2
lines changed
  • docs/examples/gitlab-ci/docker-hub-ratelimit

1 file changed

+2
-2
lines changed

docs/examples/gitlab-ci/docker-hub-ratelimit/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
2-
description: Tutorial on how to tests if GitLab CI accesses Docker Hub directly and how to configure pull-through cache to an Kubernetes cluster working as a GitLab runner.
2+
description: Tutorial on how to test if Docker-in-Docker service in GitLab CI accesses Docker Hub directly and how to configure pull-through cache to an Kubernetes cluster working as a GitLab runner.
33
---
44

5-
# Docker Hub ratelimit
5+
# Docker-in-Docker service and Docker Hub ratelimit
66

77
The recommended way of running Docker commands in a GitLab CI Kubernets runner is to use a service to run Docker-in-Docker container (`docker:dind`). By default the `docker:dind` container pulls container images from Docker Hub without caching. This can cause problems as pulls from Docker Hub are rate-limited.
88

0 commit comments

Comments
 (0)