[Bug]: Unable to launch `rapidfort/cassandra-official`

[pranavSinha0]

Name and Version

rapidfort/cassandra-official

Which runtime are you using to reproduce this issue?

• [ ] Kubernetes
• [ ] Docker Compose
• [X] Docker

Is this issue reproducible on the original source image?

Reproducible

Could you please identify the category? Details in TROUBLE_SHOOTING.md

RF error

What steps will reproduce the bug?

1. Docker pull rapidfort/cassandra-official
2. Launch the container with this image

Are you using any custom parameters or values?

No response

What is the expected behavior?

Container should have launched successfully without terminating immediately

What do you see instead?

Additional information

• Ran container-diff to find out that /etc/cassandra/cassandra-env.sh file has been removed from the rapidfort/cassandra-official image. This might be the source of error, albeit I'm not too sure about this.

[Kirandeep-Singh-Khehra]

Hi @pranavSinha0, Thaks for reportig the bug. But, is the original image behaving in same way? Please provide name and tag of image you are comparing with. and can you please also check that tags used in comparison are same or not?

Info: latest tag is not always latest. Use the tag name(not latest) to prevent confusions.

[pranavSinha0]

Hi @Kirandeep-Singh-Khehra. Original Source Image (tag: latest) cassandra runs perfectly fine.

And this experiment was ran with (tag:lastest) rapidfort/cassandra-official as well

Attaching the tags I used below for reference:

[pranavSinha0]

Commands I ran those two containers with:

For cassandra : docker run --name cassandra -d cassandra

For rapidfort-cassandra/official : docker run --name rapidfort-cassandra -d rapidfort/cassandra-official

[Kirandeep-Singh-Khehra]

@pranavSinha0 i appreciate your investigation on latest tag of both images. But here are some points:

For cassandra image:

• latest tag is a copy of 4.1.4-jammy tag or in other words cassandra:latest and cassandra:4.1.4-jammy are same(no difference at all).
• The last or highest tag added by cassandra on their docker hub repo is of 5.0 and its family. Means 5.0, 5.0-jammy, etc

For RapidFort's cassandra image:

• latest tag is a copy of 3.x tag.
• Last or highest tag added by RapidFort on our docker hub is 5.0-jammy

So, please consider these points. as it says that latest tag is not always latest/highest. Therefore use a tag name.

Keeping this issue/bug stale for some time before closing it. So, if you want to add something add in this time period.

[pranavSinha0]

@Kirandeep-Singh-Khehra I see, thank you for clearing out tag conflict and namings!

However, the issue still remains the same for tag-5.0-jammy in rapidfort/cassandra-official:5.0-jammy. Same error while running this image. This time I've compared both the images with exact same tags.

[Kirandeep-Singh-Khehra]

Thanks @pranavSinha0, This issue is present.