mirror of https://github.com/docker/docs.git
compose: fix link references
Signed-off-by: Milas Bowman <milas.bowman@docker.com>
This commit is contained in:
parent
3518db454f
commit
2241597c38
|
@ -311,11 +311,11 @@ build:
|
||||||
```
|
```
|
||||||
|
|
||||||
### secrets
|
### secrets
|
||||||
`secrets` grants access to sensitive data defined by [secrets](secrets) on a per-service build basis. Two
|
`secrets` grants access to sensitive data defined by [secrets](index.md#secrets) on a per-service build basis. Two
|
||||||
different syntax variants are supported: the short syntax and the long syntax.
|
different syntax variants are supported: the short syntax and the long syntax.
|
||||||
|
|
||||||
Compose implementations MUST report an error if the secret isn't defined in the
|
Compose implementations MUST report an error if the secret isn't defined in the
|
||||||
[`secrets`](#secrets-top-level-element) section of this Compose file.
|
[`secrets`](index.md#secrets-top-level-element) section of this Compose file.
|
||||||
|
|
||||||
#### Short syntax
|
#### Short syntax
|
||||||
|
|
||||||
|
@ -378,12 +378,12 @@ secrets:
|
||||||
|
|
||||||
Service builds MAY be granted access to multiple secrets. Long and short syntax for secrets MAY be used in the
|
Service builds MAY be granted access to multiple secrets. Long and short syntax for secrets MAY be used in the
|
||||||
same Compose file. Defining a secret in the top-level `secrets` MUST NOT imply granting any service build access to it.
|
same Compose file. Defining a secret in the top-level `secrets` MUST NOT imply granting any service build access to it.
|
||||||
Such grant must be explicit within service specification as [secrets](spec.md#secrets) service element.
|
Such grant must be explicit within service specification as [secrets](index.md#secrets) service element.
|
||||||
|
|
||||||
### tags
|
### tags
|
||||||
|
|
||||||
`tags` defines a list of tag mappings that MUST be associated to the build image. This list comes in addition of
|
`tags` defines a list of tag mappings that MUST be associated to the build image. This list comes in addition of
|
||||||
the `image` [property defined in the service section](spec.md#image)
|
the `image` [property defined in the service section](index.md#image)
|
||||||
|
|
||||||
```yml
|
```yml
|
||||||
tags:
|
tags:
|
||||||
|
@ -393,7 +393,7 @@ tags:
|
||||||
|
|
||||||
### platforms
|
### platforms
|
||||||
|
|
||||||
`platforms` defines a list of target [platforms](spec.md#platform).
|
`platforms` defines a list of target [platforms](index.md#platform).
|
||||||
|
|
||||||
```yml
|
```yml
|
||||||
build:
|
build:
|
||||||
|
|
Loading…
Reference in New Issue