From b206e8b2a45938a42f4a6d74ea38f93908e94d92 Mon Sep 17 00:00:00 2001 From: Richard Scothern Date: Fri, 14 Oct 2016 14:24:14 -0700 Subject: [PATCH] Add note about configuring a registry cache with delete enabled Signed-off-by: Richard Scothern --- docs/recipes/mirror.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/recipes/mirror.md b/docs/recipes/mirror.md index 75ea964f8..a7f80a497 100644 --- a/docs/recipes/mirror.md +++ b/docs/recipes/mirror.md @@ -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: 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 You will need to pass the `--registry-mirror` option to your Docker daemon on startup: