From fd49e78fb09d436a9c78e4a92de41db3670b11bf Mon Sep 17 00:00:00 2001 From: Victoria Bialas Date: Mon, 21 Nov 2016 11:40:28 -0800 Subject: [PATCH] clarify syntax on swarm heartbeat for create machine command Signed-off-by: Victoria Bialas --- machine/reference/create.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/machine/reference/create.md b/machine/reference/create.md index e58b7b6daa..936ae13eea 100644 --- a/machine/reference/create.md +++ b/machine/reference/create.md @@ -207,8 +207,7 @@ you can use Machine to specify how the created Swarm master should be configured. There is a `--swarm-strategy` flag, which you can use to specify the [scheduling strategy](/swarm/scheduler/strategy.md) which Docker Swarm should use (Machine defaults to the `spread` strategy). -There is also a general purpose `--swarm-opt` option which works similar to how -the aforementioned `--engine-opt` option does, except that it specifies options +There is also a general purpose `--swarm-opt` option which works similar to the aforementioned `--engine-opt` option, except that it specifies options for the `swarm manage` command (used to boot a master node) instead of the base command. You can use this to configure features that power users might be interested in, such as configuring the heartbeat interval or Swarm's willingness @@ -228,7 +227,7 @@ $ docker-machine create -d virtualbox \ --swarm-master \ --swarm-discovery token:// \ --swarm-strategy binpack \ - --swarm-opt heartbeat=5 \ + --swarm-opt heartbeat=5s \ upbeat ``` @@ -246,4 +245,4 @@ check" which is specified at the driver level. If this pre-create check succeeds, Docker Machine will proceed with the creation as normal. If the pre-create check fails, the Docker Machine process will exit with status code 3 to indicate that the source of the non-zero exit was the -pre-create check failing. \ No newline at end of file +pre-create check failing.