From 9b3481265a791d5fa8af1f1a8b4042ef215ce774 Mon Sep 17 00:00:00 2001 From: Preetha Appan Date: Fri, 29 Sep 2017 10:37:04 -0500 Subject: [PATCH] Fix grammar in containers guide. --- website/source/docs/guides/consul-containers.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/guides/consul-containers.html.md b/website/source/docs/guides/consul-containers.html.md index 20e08d34f1..b1c6f85766 100644 --- a/website/source/docs/guides/consul-containers.html.md +++ b/website/source/docs/guides/consul-containers.html.md @@ -107,7 +107,7 @@ If the container running the currently-elected Consul server leader is stopped, When a previously stopped server container is restarted using `docker start `, and it is configured to obtain a new IP, Autopilot will add it back to the set of Raft peers with the same node-id and the new IP address, after which it can participate as a server again. ## Known Issues -**All nodes changing IP addresses** Prior to Consul 0.9.3, Consul did not currently gracefully handle the situation where all nodes in the cluster running inside a container are restarted at the same time, and they all obtain new IP addresses. This has been [fixed](https://github.com/hashicorp/consul/issues/1580) since Consul 0.9.3, and requires `"raft_protocol"` to be set to `"3"` in the configs in Consul 0.9.3. Consul 1.0 makes raft protocol 3 the default. +**All nodes changing IP addresses** Prior to Consul 0.9.3, Consul did not gracefully handle the situation where all nodes in the cluster running inside a container are restarted at the same time, and they all obtain new IP addresses. This has been [fixed](https://github.com/hashicorp/consul/issues/1580) since Consul 0.9.3, and requires `"raft_protocol"` to be set to `"3"` in the configs in Consul 0.9.3. Consul 1.0 makes raft protocol 3 the default. **Snapshot close error** Due to a [known issue](https://github.com/docker/libnetwork/issues/1204) with half close support in Docker, you will see an error message `[ERR] consul: Failed to close snapshot: write tcp ->: write: broken pipe` when saving snapshots. This does not affect saving and restoring snapshots when running in Docker.