Skip to content

Commit

Permalink
Adding in points to clarify usage of official images (docker#12713)
Browse files Browse the repository at this point in the history
* Adding in points to clarify usage of official images

* Minor style update

Co-authored-by: Usha Mandya <[email protected]>
  • Loading branch information
nebuk89 and usha-mandya authored Apr 20, 2021
1 parent 30d2bd1 commit 4d2993b
Showing 1 changed file with 9 additions and 1 deletion.
10 changes: 9 additions & 1 deletion registry/recipes/mirror.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,10 @@ to the internet and fetches an image it doesn't have locally, from the Docker
repository. You can run a local registry mirror and point all your daemons
there, to avoid this extra internet traffic.

> **Note**
>
> Docker Official Images are an intellectual property of Docker. Distributing Docker Official Images to third parties without a prior agreement can constitute a violation of [Docker Terms of Service](https://www.docker.com/legal/docker-terms-service){: target="blank" rel="noopener" class=“”}.
### Alternatives

Alternatively, if the set of images you are using is well delimited, you can
Expand All @@ -29,6 +33,10 @@ relying entirely on your local registry is the simplest scenario.
It's currently not possible to mirror another private registry. Only the central
Hub can be mirrored.

> **Note**
>
> Mirrors of Docker Hub are still subject to Docker's [fair usage policy](https://www.docker.com/pricing/resource-consumption-updates){: target="blank" rel="noopener" class=“”}.
### Solution

The Registry can be configured as a pull through cache. In this mode a Registry
Expand Down Expand Up @@ -117,4 +125,4 @@ Save the file and reload Docker for the change to take effect.
> ```
>
> It's telling you that the file doesn't exist yet in the local cache and is
> being pulled from upstream.
> being pulled from upstream.

0 comments on commit 4d2993b

Please sign in to comment.