From 27a88b645e33879934c6708a585b61998a1e2f49 Mon Sep 17 00:00:00 2001 From: Brandon Philips Date: Wed, 20 May 2015 22:03:09 -0600 Subject: [PATCH] standalone: start etcd2 We are configuring etcd2 but starting the old etcd service. This will work on a single machine but isn't the user's intention. This is untested, I just wanted to fix it first. --- .../getting-started-guides/coreos/cloud-configs/standalone.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started-guides/coreos/cloud-configs/standalone.yaml b/docs/getting-started-guides/coreos/cloud-configs/standalone.yaml index efd01a15a0a..f9fd09560fa 100644 --- a/docs/getting-started-guides/coreos/cloud-configs/standalone.yaml +++ b/docs/getting-started-guides/coreos/cloud-configs/standalone.yaml @@ -13,7 +13,7 @@ coreos: initial-cluster: master=http://0.0.0.0:2380 initial-cluster-state: new units: - - name: etcd.service + - name: etcd2.service command: start - name: fleet.service command: start