registry: use relative markdown links
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
parent
267e231de0
commit
aee0eeb354
8 changed files with 13 additions and 13 deletions
|
@ -30,7 +30,7 @@ Furthermore, introducing an extra http layer in your communication pipeline adds
|
|||
|
||||
## Setting things up
|
||||
|
||||
Read again [the requirements](/registry/recipes/index.md#requirements).
|
||||
Read again [the requirements](index.md#requirements).
|
||||
|
||||
Ready?
|
||||
|
||||
|
|
|
@ -88,12 +88,12 @@ proxy:
|
|||
|
||||
> **Warning**: For the scheduler to clean up old entries, `delete` must
|
||||
> be enabled in the registry configuration. See
|
||||
> [Registry Configuration](/registry/configuration.md) for more details.
|
||||
> [Registry Configuration](../configuration.md) for more details.
|
||||
|
||||
### Configure the Docker daemon
|
||||
|
||||
Either pass the `--registry-mirror` option when starting `dockerd` manually,
|
||||
or edit [`/etc/docker/daemon.json`](/engine/reference/commandline/dockerd.md#daemon-configuration-file)
|
||||
or edit [`/etc/docker/daemon.json`](../../engine/reference/commandline/dockerd.md#daemon-configuration-file)
|
||||
and add the `registry-mirrors` key and value, to make the change persistent.
|
||||
|
||||
```json
|
||||
|
|
|
@ -74,7 +74,7 @@ properly. For more information, see
|
|||
|
||||
## Setting things up
|
||||
|
||||
Review the [requirements](/registry/recipes/index.md#requirements), then follow these steps.
|
||||
Review the [requirements](index.md#requirements), then follow these steps.
|
||||
|
||||
1. Create the required directories
|
||||
|
||||
|
|
|
@ -12,7 +12,7 @@ This is useful if you intend to run a registry server natively on macOS.
|
|||
|
||||
You can start a VM on macOS, and deploy your registry normally as a container using Docker inside that VM.
|
||||
|
||||
The simplest road to get there is traditionally to use the [docker Toolbox](https://www.docker.com/toolbox), or [docker-machine](/machine/index.md), which usually relies on the [boot2docker](http://boot2docker.io/) ISO inside a VirtualBox VM.
|
||||
The simplest road to get there is traditionally to use the [docker Toolbox](https://www.docker.com/toolbox), or [docker-machine](../../machine/index.md), which usually relies on the [boot2docker](http://boot2docker.io/) ISO inside a VirtualBox VM.
|
||||
|
||||
### Solution
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue