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

added clarification to swarm configs and stack deploy topic (#5159) 

Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
This commit is contained in:
Victoria Bialas 2017-10-30 14:20:40 -07:00 committed by GitHub
parent 0e1dcd9db9
commit 81270cbd7d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
engine/swarm/configs.md
View File

@ -61,6 +61,17 @@ In order to update or roll back configs more easily, consider adding a version
number or date to the config name. This is made easier by the ability to control number or date to the config name. This is made easier by the ability to control
the mount point of the config within a given container. the mount point of the config within a given container.
To update a stack, make changes to your Compose file, then re-run `docker
stack deploy -c <new-compose-file> <stack-name>`. If you use a new config in
that file, your services will start using them. Keep in mind that configurations
are immutable, so you won't be able to change the file for an existing service.
Instead, you create a new config to use a different file
You can run `docker stack rm` to stop the app and take down the stack. This
removes any config that was created by `docker stack deploy` with the same stack
name. This removes _all_ configs, including those not referenced by services and
those remaining after a `docker service update --config-rm`.
## Read more about `docker config` commands ## Read more about `docker config` commands
Use these links to read about specific commands, or continue to the Use these links to read about specific commands, or continue to the