fill the complete address because of no userguide directory

Signed-off-by: lixiaobing10051267 <li.xiaobing1@zte.com.cn>
This commit is contained in:
lixiaobing10051267 2016-10-27 16:24:55 +08:00 committed by Tibor Vass
parent 836b1a7d0a
commit 2603a9c1dd
4 changed files with 8 additions and 8 deletions

View File

@ -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`. 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 - The [LibNetwork](https://github.com/docker/libnetwork) project

View File

@ -23,7 +23,7 @@ instructions in succession.
This page describes the commands you can use in a `Dockerfile`. When you are This page describes the commands you can use in a `Dockerfile`. When you are
done reading this page, refer to the [`Dockerfile` Best 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 ## Usage
@ -92,7 +92,7 @@ instructions.
Whenever possible, Docker will re-use the intermediate images (cache), Whenever possible, Docker will re-use the intermediate images (cache),
to accelerate the `docker build` process significantly. This is indicated by to accelerate the `docker build` process significantly. This is indicated by
the `Using cache` message in the console output. 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: `Dockerfile` best practices guide:
$ docker build -t svendowideit/ambassador . $ docker build -t svendowideit/ambassador .
@ -573,7 +573,7 @@ cache for `RUN` instructions can be invalidated by using the `--no-cache`
flag, for example `docker build --no-cache`. flag, for example `docker build --no-cache`.
See the [`Dockerfile` Best Practices 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 The cache for `RUN` instructions can be invalidated by `ADD` instructions. See
[below](#add) for details. [below](#add) for details.
@ -728,7 +728,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 flag](run.md#expose-incoming-ports). The Docker network feature supports
creating networks without the need to expose ports within the network, for creating networks without the need to expose ports within the network, for
detailed information see the [overview of this detailed information see the [overview of this
feature](../userguide/networking/index.md)). feature](https://docs.docker.com/engine/userguide/networking/)).
## ENV ## ENV
@ -829,7 +829,7 @@ of whether or not the file has changed and the cache should be updated.
> following instructions from the Dockerfile if the contents of `<src>` have > following instructions from the Dockerfile if the contents of `<src>` have
> changed. This includes invalidating the cache for `RUN` instructions. > changed. This includes invalidating the cache for `RUN` instructions.
> See the [`Dockerfile` Best Practices > 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: `ADD` obeys the following rules:

View File

@ -37,7 +37,7 @@ n2
* [network ls](network_ls.md) * [network ls](network_ls.md)
* [network inspect](network_inspect.md) * [network inspect](network_inspect.md)
* [network rm](network_rm.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) * [system df](system_df.md)
* [container prune](container_prune.md) * [container prune](container_prune.md)
* [image prune](image_prune.md) * [image prune](image_prune.md)

View File

@ -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 default bridge network, then the client container can access the exposed
port via a private networking interface. port via a private networking interface.
If `--link` is used when starting a container in a user-defined network as 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. it will provide a named alias for the container being linked to.
### ENV (environment variables) ### ENV (environment variables)