Cassandra 4.1.2 Image does not run with docker.

Summary

Running the docker image locally fails with the below exception

Starting Management API
Running java -Xms128m -Xmx128m -jar /opt/management-api/datastax-mgmtapi-server.jar
/opt/management-api/datastax-mgmtapi-server-0.1.0-SNAPSHOT.jar --cassandra-socket /tmp/cassandra.sock --host tcp://0.0.0.0:8080 --host file:///tmp/oss-mgmt.sock --cassandra-home /opt/cassandra
Error: Unable to access jarfile /opt/management-api/datastax-mgmtapi-server.jar
/opt/management-api/datastax-mgmtapi-server-0.1.0-SNAPSHOT.jar

Steps to reproduce

docker run -v $PWD/tmp/cassandra:/var/lib/cassandra/:Z <registry>/ironbank/opensource/k8ssandra/cass-management-api:4.1.2

What is the current bug behavior?

Looks like the command generated when the image starts contains 2 jars (opt/management-api/datastax-mgmtapi-server.jar /opt/management-api/datastax-mgmtapi-server-0.1.0-SNAPSHOT.jar ) instead of one while starting the management api.

What is the expected correct behavior?

On startup the container should run with cassandra enabled.

Relevant logs and/or screenshots

Possible fixes

The command in the ./docker-entrypoint.sh file returns two values instead of one.

[cassandra@4b2072335a12 /]$ find "${MAAC_PATH}" -name *server*.jar
/opt/management-api/datastax-mgmtapi-server.jar
/opt/management-api/datastax-mgmtapi-server-0.1.0-SNAPSHOT.jar

We could only copy the necessary jars when we build the dockerfile or just change the command to exclude symbolic links

find "${MAAC_PATH}" -name *server*.jar -type f

Tasks

• Bug has been identified and corrected within the container

Please read the Iron Bank Documentation for more info