0.3.1 and bootstrap expect

Dockerfile

@@ -1,10 +1,10 @@
 FROM 		progrium/busybox 
 MAINTAINER 	Jeff Lindsay <[email protected]>
 
-ADD https://dl.bintray.com/mitchellh/consul/0.3.0_linux_amd64.zip /tmp/consul.zip
+ADD https://dl.bintray.com/mitchellh/consul/0.3.1_linux_amd64.zip /tmp/consul.zip
 RUN cd /bin && unzip /tmp/consul.zip && chmod +x /bin/consul && rm /tmp/consul.zip
 
-ADD https://dl.bintray.com/mitchellh/consul/0.3.0_web_ui.zip /tmp/webui.zip
+ADD https://dl.bintray.com/mitchellh/consul/0.3.1_web_ui.zip /tmp/webui.zip
 RUN cd /tmp && unzip /tmp/webui.zip && mv dist /ui && rm /tmp/webui.zip
 
 RUN opkg-install curl bash

README.md

@@ -111,7 +111,7 @@ And the third host with an IP of 10.0.1.3:
 
 Once the third host is running, you want to go back to the second host, kill the container, and run it again just as before but without the `-bootstrap` flag. You'd then have a full cluster running in production on a private network.
 
-There is currently an issue when you restart the bootstrap node as a new container with the same publish IP that will cause heartbeats to fail and the node will flap. This is because of an ARP table cache problem. If you wait about 3-5 minutes before starting again, it should work fine. This issue will be dissolved with the "auto-bootstrapping" capability of Consul 0.4.0.
+There is currently an issue when you restart the bootstrap node as a new container with the same published ports that will cause heartbeats to fail and the node will flap. I believe this is because of an ARP table caching problem. If you wait about 3 minutes before starting again, it should work fine. This issue will be dissolved with the "auto-bootstrapping" capability of Consul 0.4.0.
 
 ## Opinionated Configuration
 

start

@@ -10,7 +10,7 @@ cmd-run() {
 
 	IFS=':' read external_ip join_ip <<< "${ip_def/::/:}"
 	if [[ -z "$join_ip" ]]; then
-		run_mode="-bootstrap"
+		run_mode="-bootstrap-expect 3"
 	else
 		run_mode="-join $join_ip"
 	fi