From fcbe16b90eaa2608403f5b9e4f95e79229fddee4 Mon Sep 17 00:00:00 2001
From: Docker Library Bot <github+dockerlibrarybot@infosiftr.com>
Date: Tue, 30 Oct 2018 22:09:14 +0000
Subject: [PATCH] Run update.sh

---
 cassandra/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/cassandra/README.md b/cassandra/README.md
index a14d2d5f3..d3f2605bf 100644
--- a/cassandra/README.md
+++ b/cassandra/README.md
@@ -82,7 +82,7 @@ $ docker run --name some-app --link some-cassandra:cassandra -d app-that-uses-ca
 Using the environment variables documented below, there are two cluster scenarios: instances on the same machine and instances on separate machines. For the same machine, start the instance as described above. To start other instances, just tell each new node where the first is.
 
 ```console
-$ docker run --name some-cassandra2 -d -e CASSANDRA_SEEDS="$(docker inspect --format='{{ .NetworkSettings.IPAddress }}' some-cassandra)" cassandra:tag
+$ docker run --name some-cassandra2 -d -e CASSANDRA_SEEDS="$(docker inspect --format='{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' some-cassandra)" cassandra:tag
 ```
 
 ... 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.