From 81270cbd7da8c0b51a7bf9a8ae56d880d64c1d38 Mon Sep 17 00:00:00 2001 From: Victoria Bialas Date: Mon, 30 Oct 2017 14:20:40 -0700 Subject: [PATCH] added clarification to swarm configs and stack deploy topic (#5159) Signed-off-by: Victoria Bialas --- engine/swarm/configs.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/engine/swarm/configs.md b/engine/swarm/configs.md index 274f259ff1..931f584b73 100644 --- a/engine/swarm/configs.md +++ b/engine/swarm/configs.md @@ -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 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 `. 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 Use these links to read about specific commands, or continue to the