We recently noticed that we had locked up Cassandra Docker containers piling up when running our integration tests.
After digging around some more, we saw some others complaining of similar symptoms. Something in common with all cases was the use of Cassandra 2.1.x images. After seeing someone mention that Cassandra 2.2 and 3.x images weren't showing this behavior, we gave it a shot.
As luck would have it, this did the trick! So for anyone else running into Cassandra Docker containers with the following symptoms, consider switching to 2.2+:
- Containers never fully start, hanging after creation.
- Containers can't be rm'd or killed.
- docker logs shows no output in addition the the previous two.