Fix `depends_on` links across documents. (#4424)

NOTE: compose file v1 doesn't support `depends_on`,
      thus it's still a broken link.

Signed-off-by: Wenxuan Zhao <viz@linux.com>
This commit is contained in:
Wenxuan Zhao 2017-08-29 19:52:02 -03:00 committed by Misty Stanley-Jones
parent 0688b894ca
commit 4d43ae7ea2
4 changed files with 4 additions and 4 deletions

View File

@ -365,7 +365,7 @@ Containers for the linked service will be reachable at a hostname identical to
the alias, or the service name if no alias was specified.
Links also express dependency between services in the same way as
[depends_on](#dependson), so they determine the order of service startup.
[depends_on](#depends_on), so they determine the order of service startup.
> **Note**: If you define both links and [networks](#networks), services with
> links between them must share at least one network in common in order to

View File

@ -638,7 +638,7 @@ Containers for the linked service will be reachable at a hostname identical to
the alias, or the service name if no alias was specified.
Links also express dependency between services in the same way as
[depends_on](#dependson), so they determine the order of service startup.
[depends_on](#depends_on), so they determine the order of service startup.
> **Note**: If you define both links and [networks](#networks), services with
> links between them must share at least one network in common in order to

View File

@ -166,7 +166,7 @@ Several other options were added to support networking, such as:
* [`aliases`](compose-file-v2.md#aliases)
* The [`depends_on`](compose-file-v2.md#dependson) option can be used in place of links to indicate dependencies
* The [`depends_on`](compose-file-v2.md#depends_on) option can be used in place of links to indicate dependencies
between services and startup order.
version: '2'

View File

@ -1093,7 +1093,7 @@ any service can reach any other service at that services name. (See also, the
[Links topic in Networking in Compose](/compose/networking.md#links).)
Links also express dependency between services in the same way as
[depends_on](#dependson), so they determine the order of service startup.
[depends_on](#depends_on), so they determine the order of service startup.
> **Notes**
>