From 97c00f9754271bbc03c6309793482e11920e4f3e Mon Sep 17 00:00:00 2001 From: lixiaobing10051267 Date: Thu, 27 Oct 2016 16:24:55 +0800 Subject: [PATCH] fill the complete address because of no userguide directory Signed-off-by: lixiaobing10051267 --- docs/extend/plugins_network.md | 2 +- docs/reference/api/hub_registry_spec.md | 2 +- docs/reference/builder.md | 10 +++++----- docs/reference/commandline/network_prune.md | 2 +- docs/reference/run.md | 2 +- 5 files changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/extend/plugins_network.md b/docs/extend/plugins_network.md index 9546195bbd..095c143f74 100644 --- a/docs/extend/plugins_network.md +++ b/docs/extend/plugins_network.md @@ -73,5 +73,5 @@ documented as part of libnetwork: To interact with the Docker maintainers and other interested users, see the IRC channel `#docker-network`. -- [Docker networks feature overview](../userguide/networking/index.md) +- [Docker networks feature overview](https://docs.docker.com/engine/userguide/networking/) - The [LibNetwork](https://github.com/docker/libnetwork) project diff --git a/docs/reference/api/hub_registry_spec.md b/docs/reference/api/hub_registry_spec.md index e4de606a6d..37a60a94a6 100644 --- a/docs/reference/api/hub_registry_spec.md +++ b/docs/reference/api/hub_registry_spec.md @@ -20,4 +20,4 @@ This API is deprecated as of 1.7. To view the old version, see the [go here](https://docs.docker.com/v1.7/docker/reference/api/hub_registry_spec/) in the 1.7 documentation. If you want an overview of the current features in Docker Hub or other image management features see the [image management -overview](../../userguide/eng-image/image_management.md) in the current documentation set. +overview](https://docs.docker.com/engine/userguide/eng-image/image_management/) in the current documentation set. diff --git a/docs/reference/builder.md b/docs/reference/builder.md index 19e693482f..160fd86d0e 100644 --- a/docs/reference/builder.md +++ b/docs/reference/builder.md @@ -23,7 +23,7 @@ instructions in succession. This page describes the commands you can use in a `Dockerfile`. When you are done reading this page, refer to the [`Dockerfile` Best -Practices](../userguide/eng-image/dockerfile_best-practices.md) for a tip-oriented guide. +Practices](https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/) for a tip-oriented guide. ## Usage @@ -92,7 +92,7 @@ instructions. Whenever possible, Docker will re-use the intermediate images (cache), to accelerate the `docker build` process significantly. This is indicated by the `Using cache` message in the console output. -(For more information, see the [Build cache section](../userguide/eng-image/dockerfile_best-practices.md#build-cache)) in the +(For more information, see the [Build cache section](https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/#/build-cache)) in the `Dockerfile` best practices guide: $ docker build -t svendowideit/ambassador . @@ -574,7 +574,7 @@ cache for `RUN` instructions can be invalidated by using the `--no-cache` flag, for example `docker build --no-cache`. See the [`Dockerfile` Best Practices -guide](../userguide/eng-image/dockerfile_best-practices.md#build-cache) for more information. +guide](https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/#/build-cache) for more information. The cache for `RUN` instructions can be invalidated by `ADD` instructions. See [below](#add) for details. @@ -729,7 +729,7 @@ To set up port redirection on the host system, see [using the -P flag](run.md#expose-incoming-ports). The Docker network feature supports creating networks without the need to expose ports within the network, for detailed information see the [overview of this -feature](../userguide/networking/index.md)). +feature](https://docs.docker.com/engine/userguide/networking/)). ## ENV @@ -830,7 +830,7 @@ of whether or not the file has changed and the cache should be updated. > following instructions from the Dockerfile if the contents of `` have > changed. This includes invalidating the cache for `RUN` instructions. > See the [`Dockerfile` Best Practices -guide](../userguide/eng-image/dockerfile_best-practices.md#build-cache) for more information. +guide](https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/#/build-cache) for more information. `ADD` obeys the following rules: diff --git a/docs/reference/commandline/network_prune.md b/docs/reference/commandline/network_prune.md index 82da94e31c..f0db94724a 100644 --- a/docs/reference/commandline/network_prune.md +++ b/docs/reference/commandline/network_prune.md @@ -37,7 +37,7 @@ n2 * [network ls](network_ls.md) * [network inspect](network_inspect.md) * [network rm](network_rm.md) -* [Understand Docker container networks](../../userguide/networking/index.md) +* [Understand Docker container networks](https://docs.docker.com/engine/userguide/networking/) * [system df](system_df.md) * [container prune](container_prune.md) * [image prune](image_prune.md) diff --git a/docs/reference/run.md b/docs/reference/run.md index a48b44d4bf..b1fef2b12e 100644 --- a/docs/reference/run.md +++ b/docs/reference/run.md @@ -1376,7 +1376,7 @@ If the operator uses `--link` when starting a new client container in the default bridge network, then the client container can access the exposed port via a private networking interface. If `--link` is used when starting a container in a user-defined network as -described in [*Docker network overview*](../userguide/networking/index.md), +described in [*Docker network overview*](https://docs.docker.com/engine/userguide/networking/), it will provide a named alias for the container being linked to. ### ENV (environment variables)