Currently, the sed matches and replaces the seeds configuration only on the first run when the seeds is set to 127.0.0.1.
Considering the use case for this image is development, it is very likely that the container will not always be allocated the same ip. If the seeds ip is not correct, gossip will fail and cassandra will shutdown.
Currently, the sed matches and replaces the seeds configuration only on the first run when the seeds is set to 127.0.0.1.
Considering the use case for this image is development, it is very likely that the container will not always be allocated the same ip. If the seeds ip is not correct, gossip will fail and cassandra will shutdown.
Proposed solution: #14