Run update.sh

This commit is contained in:
Docker Library Bot 2015-12-01 16:01:32 -08:00
parent 4148885245
commit 33f5646c0a
1 changed files with 6 additions and 0 deletions

View File

@ -46,6 +46,12 @@ $ docker run --name some-cassandra2 -d -e CASSANDRA_SEEDS="$(docker inspect --fo
... where `some-cassandra` is the name of your original Cassandra Server container, taking advantage of `docker inspect` to get the IP address of the other container. ... where `some-cassandra` is the name of your original Cassandra Server container, taking advantage of `docker inspect` to get the IP address of the other container.
Or you may use the docker run --link option to tell the new node where the first is:
```console
$ docker run --name some-cassandra2 -d --link some-cassandra:cassandra cassandra:tag
```
For separate machines (ie, two VMs on a cloud provider), you need to tell Cassandra what IP address to advertise to the other nodes (since the address of the container is behind the docker bridge). For separate machines (ie, two VMs on a cloud provider), you need to tell Cassandra what IP address to advertise to the other nodes (since the address of the container is behind the docker bridge).
Assuming the first machine's IP address is `10.42.42.42` and the second's is `10.43.43.43`, start the first with exposed gossip port: Assuming the first machine's IP address is `10.42.42.42` and the second's is `10.43.43.43`, start the first with exposed gossip port: