docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Engdocs 2002: minor triage on compose issues (#19511) 

* clarify base compose file meaning

* update name example and reformat link
This commit is contained in:
Allie Sadler 2024-02-27 08:06:39 +00:00 committed by GitHub
parent ea15065d69
commit c01d60a858
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/compose/compose-file/04-version-and-name.md
View File

@ -24,11 +24,11 @@ Whenever a project name is defined by top-level `name` or by some custom mechani
[interpolation](12-interpolation.md) and environment variable resolution as `COMPOSE_PROJECT_NAME` [interpolation](12-interpolation.md) and environment variable resolution as `COMPOSE_PROJECT_NAME`
```yml ```yml
name: myapp
services: services:
foo: foo:
image: busybox image: busybox
environment:
- COMPOSE_PROJECT_NAME
command: echo "I'm running ${COMPOSE_PROJECT_NAME}" command: echo "I'm running ${COMPOSE_PROJECT_NAME}"
``` ```

2
content/compose/compose-file/09-secrets.md
View File

@ -6,7 +6,7 @@ keywords: compose, compose specification, secrets, compose file reference
Secrets are a flavor of [Configs](08-configs.md) focusing on sensitive data, with specific constraint for this usage. Secrets are a flavor of [Configs](08-configs.md) focusing on sensitive data, with specific constraint for this usage.
Services can only access secrets when explicitly granted by a [`secrets`](05-services.md#secrets) attribute within the `services` top-level element. Services can only access secrets when explicitly granted by a [`secrets` attribute](05-services.md#secrets) within the `services` top-level element.
The top-level `secrets` declaration defines or references sensitive data that is granted to the services in your Compose The top-level `secrets` declaration defines or references sensitive data that is granted to the services in your Compose
application. The source of the secret is either `file` or `environment`. application. The source of the secret is either `file` or `environment`.

2
content/compose/multiple-compose-files/extends.md
View File

@ -20,7 +20,7 @@ application, with the ability to override some attributes for your own needs.
> **Important** > **Important**
> >
> When you use multiple Compose files, you must make sure all paths in the files > When you use multiple Compose files, you must make sure all paths in the files
are relative to the base Compose file. This is required because extend files are relative to the base Compose file (i.e. the Compose file in your main-project folder). This is required because extend files
need not be valid Compose files. Extend files can contain small fragments of need not be valid Compose files. Extend files can contain small fragments of
configuration. Tracking which fragment of a service is relative to which path is configuration. Tracking which fragment of a service is relative to which path is
difficult and confusing, so to keep paths easier to understand, all paths must difficult and confusing, so to keep paths easier to understand, all paths must