docker-library
/
docs
mirror of https://github.com/docker-library/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix running consul for development 

At least under ``Docker version 17.07.0-ce-rc4``,  running consul for development does not work
without being explicit about ``CONSUL_BIND_INTERFACE``
This commit is contained in:
Godefroid Chapelle 2017-10-11 17:41:54 +02:00 committed by GitHub
parent 17604adc26
commit e46559a039
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
consul/content.md
View File

@ -38,15 +38,15 @@ The entry point also includes a small utility to look up a client or bind addres
## Running Consul for Development
```console
$ docker run -d --name=dev-consul %%IMAGE%%
$ docker run -d --name=dev-consul -e CONSUL_BIND_INTERFACE=eth0 %%IMAGE%%
```
This runs a completely in-memory Consul server agent with default bridge networking and no services exposed on the host, which is useful for development but should not be used in production. For example, if that server is running at internal address 172.17.0.2, you can run a three node cluster for development by starting up two more instances and telling them to join the first node.
```console
$ docker run -d %%IMAGE%% agent -dev -join=172.17.0.2
$ docker run -d -e CONSUL_BIND_INTERFACE=eth0 %%IMAGE%% agent -dev -join=172.17.0.2
... server 2 starts
$ docker run -d %%IMAGE%% agent -dev -join=172.17.0.2
$ docker run -d -e CONSUL_BIND_INTERFACE=eth0 %%IMAGE%% agent -dev -join=172.17.0.2
... server 3 starts
```