Merge pull request #222 from thaJeztah/carry-moby-33290

Explain `stack deploy` with multiple Compose files
This commit is contained in:
Vincent Demeester 2017-06-21 17:36:20 +02:00 committed by GitHub
commit 4b1055aaa6
1 changed files with 23 additions and 2 deletions

View File

@ -40,7 +40,7 @@ has to be run targeting a manager node.
### Compose file ### Compose file
The `deploy` command supports compose file version `3.0` and above." The `deploy` command supports compose file version `3.0` and above.
```bash ```bash
$ docker stack deploy --compose-file docker-compose.yml vossibility $ docker stack deploy --compose-file docker-compose.yml vossibility
@ -57,7 +57,28 @@ Creating service vossibility_ghollector
Creating service vossibility_lookupd Creating service vossibility_lookupd
``` ```
You can verify that the services were correctly created Only a single Compose file is accepted. If your configuration is split between
multiple Compose files, e.g. a base configuration and environment-specific overrides,
you can combine these by passing them to `docker-compose config` with the `-f` option
and redirecting the merged output into a new file.
```bash
$ docker-compose -f docker-compose.yml -f docker-compose.prod.yml config > docker-stack.yml
$ docker stack deploy --compose-file docker-stack.yml vossibility
Ignoring unsupported options: links
Creating network vossibility_vossibility
Creating network vossibility_default
Creating service vossibility_nsqd
Creating service vossibility_logstash
Creating service vossibility_elasticsearch
Creating service vossibility_kibana
Creating service vossibility_ghollector
Creating service vossibility_lookupd
```
You can verify that the services were correctly created:
```bash ```bash
$ docker service ls $ docker service ls