fcrozat/distribution
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update mirror.md

Browse Source 
It was not obvious that additional configuration is needed for the official Registry image.

cc @dmcgowan @stevvooe
This commit is contained in:
Akihiro Suda 2018-02-14 17:23:34 +09:00 committed by Joao Fernandes
parent 947af10cc0
commit db6444ace5
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/recipes/mirror.md
View File

@ -59,6 +59,8 @@ be configured to use the `filesystem` driver for storage.
The easiest way to run a registry as a pull through cache is to run the official The easiest way to run a registry as a pull through cache is to run the official
Registry image. Registry image.
At least, you need to specify `proxy.remoteurl` within `/etc/docker/registry/config.yml`
as described in the following subsection.
Multiple registry caches can be deployed over the same back-end. A single Multiple registry caches can be deployed over the same back-end. A single
registry cache ensures that concurrent requests do not pull duplicate data, registry cache ensures that concurrent requests do not pull duplicate data,