dkirillov/distribution
1
0
Fork 0
forked from TrueCloudLab/distribution
Code Pull requests Activity

Add note about configuring a registry cache with delete enabled

Browse source 
Signed-off-by: Richard Scothern <richard.scothern@gmail.com>
This commit is contained in:
Richard Scothern 2016-10-14 14:24:14 -07:00
parent 50bd0cce07
commit b206e8b2a4
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

@ -62,6 +62,8 @@ In order to access private images on the Docker Hub, a username and password can
> :warn: if you specify a username and password, it's very important to understand that private resources that this user has access to on the Hub will be made available on your mirror. It's thus paramount that you secure your mirror by implementing authentication if you expect these resources to stay private! > :warn: if you specify a username and password, it's very important to understand that private resources that this user has access to on the Hub will be made available on your mirror. It's thus paramount that you secure your mirror by implementing authentication if you expect these resources to stay private!
> :warn: in order for the scheduler to clean up old entries, delete must be enabled in the registry configuration. See the [Registry Configuration Reference](configuration.md) for more details.
### Configuring the Docker daemon ### Configuring the Docker daemon
You will need to pass the `--registry-mirror` option to your Docker daemon on startup: You will need to pass the `--registry-mirror` option to your Docker daemon on startup: