From 78d7e2b788b5bf3c4be658767ef4cc697f332616 Mon Sep 17 00:00:00 2001 From: Yang Li Date: Tue, 17 Oct 2017 16:51:57 +0800 Subject: [PATCH] fix docker docs link --- contrib/Configure_mirror.md | 54 ++++++++++++++++++------------------- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/contrib/Configure_mirror.md b/contrib/Configure_mirror.md index 00badf130..3b01742f7 100644 --- a/contrib/Configure_mirror.md +++ b/contrib/Configure_mirror.md @@ -1,30 +1,30 @@ -# Configuring Harbor as a local registry mirror +# Configuring Harbor as a local registry mirror Harbor runs as a local registry by default. It can also be configured as a registry mirror, which caches downloaded images for subsequent use. Note that under this setup, the Harbor registry only acts as a mirror server and -no longer accepts image pushing requests. Edit `Deploy/templates/registry/config.yml` before executing `./prepare`, and append a `proxy` section as follows: - -``` -proxy: - remoteurl: https://registry-1.docker.io -``` -In order to access private images on the Docker Hub, a username and a password can be supplied: - -``` -proxy: - remoteurl: https://registry-1.docker.io - username: [username] - password: [password] -``` -You will need to pass the `--registry-mirror` option to your Docker daemon on startup: - -``` -docker --registry-mirror=https:// daemon -``` -For example, if your mirror is serving on `http://reg.yourdomain.com`, you would run: - -``` -docker --registry-mirror=https://reg.yourdomain.com daemon -``` - -Refer to the [Registry as a pull through cache](https://github.com/docker/distribution/blob/master/docs/mirror.md) for detailed information. +no longer accepts image pushing requests. Edit `Deploy/templates/registry/config.yml` before executing `./prepare`, and append a `proxy` section as follows: + +``` +proxy: + remoteurl: https://registry-1.docker.io +``` +In order to access private images on the Docker Hub, a username and a password can be supplied: + +``` +proxy: + remoteurl: https://registry-1.docker.io + username: [username] + password: [password] +``` +You will need to pass the `--registry-mirror` option to your Docker daemon on startup: + +``` +docker --registry-mirror=https:// daemon +``` +For example, if your mirror is serving on `http://reg.yourdomain.com`, you would run: + +``` +docker --registry-mirror=https://reg.yourdomain.com daemon +``` + +Refer to the [Registry as a pull through cache](https://docs.docker.com/registry/recipes/mirror/) for detailed information.