engine: call out compose file format used by swarm

Signed-off-by: David Karlsson <david.karlsson@docker.com>
This commit is contained in:
David Karlsson 2023-05-27 20:14:28 +02:00
parent 093181c9e1
commit 5206d4853b
3 changed files with 16 additions and 2 deletions

View File

@ -0,0 +1,10 @@
> **Note**
>
> The `docker stack deploy` command uses the legacy
> [Compose file version 3](/compose/compose-file/compose-file-v3/)
> format, used by Compose V1. The latest format, defined by the
> [Compose specification](/compose/compose-file/)
> isn't compatible with the `docker stack deploy` command.
>
> For more information about the evolution of Compose, see
> [History of Compose](/compose/history/).

View File

@ -8,8 +8,10 @@ When running Docker Engine in swarm mode, you can use `docker stack deploy` to
deploy a complete application stack to the swarm. The `deploy` command accepts
a stack description in the form of a [Compose file](../../compose/compose-file/compose-file-v3.md).
The `docker stack deploy` command supports any Compose file of version "3.0" or
above. If you have an older version, see the [upgrade guide](../../compose/compose-file/compose-versioning.md#upgrading).
{% include swarm-compose-compat.md %}
The `docker stack deploy` command supports any Compose file of version "3.x".
If you have an older version, see the [upgrade guide](../../compose/compose-file/compose-versioning.md#upgrading).
To run through this tutorial, you need:

View File

@ -28,6 +28,8 @@ Swarm never creates individual containers like we did in the previous step of th
Let's write a simple stack file to run and manage our Todo app, the container `getting-started` image created in [Part 2](02_our_app.md) of the Quickstart tutorial. Place the following in a file called `bb-stack.yaml`:
{% include swarm-compose-compat.md %}
```yaml
version: '3.7'