From 6c3bae43173072c36f4c5b02eb8bdeb3f5a8bd78 Mon Sep 17 00:00:00 2001 From: Maria Bermudez Date: Thu, 27 Sep 2018 16:54:23 -0700 Subject: [PATCH] Update services.md Fixes [7435](https://github.com/docker/docker.github.io/issues/7435) --- engine/swarm/services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/engine/swarm/services.md b/engine/swarm/services.md index a045df39b0..23fcd7f2cb 100644 --- a/engine/swarm/services.md +++ b/engine/swarm/services.md @@ -621,7 +621,7 @@ labels to ensure that your service is deployed to the appropriate swarm nodes. Use placement constraints to control the nodes a service can be assigned to. In the following example, the service only runs on nodes with the -[label](engine/swarm/manage-nodes.md#add-or-remove-label-metadata) `region` set +[label](manage-nodes.md#add-or-remove-label-metadata) `region` set to `east`. If no appropriately-labelled nodes are available, tasks will wait in `Pending` until they become available. The `--constraint` flag uses an equality operator (`==` or `!=`). For replicated services, it is possible that all