Apache Cassandra is a free and open-source distributed database management system designed to handle large amounts of data across many commodity servers, providing high availability with no single point of failure. Cassandra offers robust support for clusters spanning multiple datacenters, with asynchronous masterless replication allowing low latency operations for all clients.
$ docker run --name cassandra bitnami/cassandra:latest$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-cassandra/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d- Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
- With Bitnami images the latest bug fixes and features are available as soon as possible.
- Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
- All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading linux distribution.
- All Bitnami images available in Docker Hub are signed with Docker Content Trust (DTC). You can use
DOCKER_CONTENT_TRUST=1to verify the integrity of the images. - Bitnami container images are released daily with the latest distribution packages available.
This CVE scan report contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.
Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers in our docs.
Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami Cassandra Chart GitHub repository.
Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.
Subscribe to project updates by watching the bitnami/cassandra GitHub repo.
The recommended way to get the Bitnami Cassandra Docker Image is to pull the prebuilt image from the Docker Hub Registry.
$ docker pull bitnami/cassandra:latestTo use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.
$ docker pull bitnami/cassandra:[TAG]If you wish, you can also build the image yourself.
$ docker build -t bitnami/cassandra:latest 'https://github.com/bitnami/bitnami-docker-cassandra.git#master:3/debian-10'If you remove the container all your data and configurations will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
For persistence you should mount a directory at the /bitnami path. If the mounted directory is empty, it will be initialized on the first run.
$ docker run \
-v /path/to/cassandra-persistence:/bitnami \
bitnami/cassandra:latestor using Docker Compose:
cassandra:
image: bitnami/cassandra:latest
volumes:
- /path/to/cassandra-persistence:/bitnamiNOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID
1001.
Using Docker container networking, a Cassandra server running inside a container can easily be accessed by your application containers.
Containers attached to the same network can communicate with each other using the container name as the hostname.
In this example, we will create a Cassandra client instance that will connect to the server instance that is running on the same docker network as the client.
$ docker network create app-tier --driver bridgeUse the --network app-tier argument to the docker run command to attach the Cassandra container to the app-tier network.
$ docker run -d --name cassandra-server \
--network app-tier \
bitnami/cassandra:latestFinally we create a new container instance to launch the Cassandra client and connect to the server created in the previous step:
$ docker run -it --rm \
--network app-tier \
bitnami/cassandra:latest cqlsh --username cassandra --password cassandra cassandra-serverWhen not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new bridge network named app-tier. In this example we assume that you want to connect to the Cassandra server from your own custom application image which is identified in the following snippet by the service name myapp.
version: '2'
networks:
app-tier:
driver: bridge
services:
cassandra:
image: 'bitnami/cassandra:latest'
networks:
- app-tier
myapp:
image: 'YOUR_APPLICATION_IMAGE'
networks:
- app-tierIMPORTANT:
- Please update the YOUR_APPLICATION_IMAGE_ placeholder in the above snippet with your application image
- In your application container, use the hostname
cassandrato connect to the Cassandra server
Launch the containers using:
$ docker-compose up -dWhen you start the cassandra image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the docker run command line. If you want to add a new environment variable:
- For docker-compose add the variable name and value under the application section:
cassandra:
image: bitnami/cassandra:latest
environment:
- CASSANDRA_TRANSPORT_PORT_NUMBER=7000- For manual execution add a
-eoption with each variable and value:
$ docker run --name cassandra -d -p 7000:7000 --network=cassandra_network \
-e CASSANDRA_TRANSPORT_PORT_NUMBER=7000 \
-v /your/local/path/bitnami/cassandra:/bitnami \
bitnami/cassandraIn case you do not mount custom configuration files, the following variables are available for configuring cassandra:
CASSANDRA_TRANSPORT_PORT_NUMBER: Inter-node cluster communication port. Default: 7000CASSANDRA_JMX_PORT_NUMBER: JMX connections port. Default: 7199CASSANDRA_CQL_PORT_NUMBER: Client port. Default: 9042.CASSANDRA_USER: Cassandra user name. Defaults: cassandraCASSANDRA_PASSWORD_SEEDER: Password seeder will change the Cassandra default credentials at initialization. In clusters, only one node should be marked as password seeder. Default: noCASSANDRA_PASSWORD: Cassandra user password. Default: cassandraCASSANDRA_NUM_TOKENS: Number of tokens for the node. Default: 256.CASSANDRA_HOST: Hostname used to configure Cassandra. It can be either an IP or a domain. If left empty, it will be resolved to the machine IP.CASSANDRA_CLUSTER_NAME: Cluster name to configure Cassandra.. Defaults: My ClusterCASSANDRA_SEEDS: Hosts that will act as Cassandra seeds. No defaults.CASSANDRA_ENDPOINT_SNITCH: Snitch name (which determines which data centers and racks nodes belong to). Default SimpleSnitchCASSANDRA_ENABLE_RPC: Enable the thrift RPC endpoint. Default :trueCASSANDRA_DATACENTER: Datacenter name for the cluster. Ignored in SimpleSnitch endpoint snitch. Default: dc1.CASSANDRA_RACK: Rack name for the cluster. Ignored in SimpleSnitch endpoint snitch. Default: rack1.- 'CASSANDRA_ENABLE_USER_DEFINED_FUNCTIONS': User defined functions. Default : false.
The image looks for configurations in /opt/bitnami/cassandra/conf/. You can mount a volume at /bitnami/cassandra/conf/ and copy/edit the configurations in the /path/to/cassandra-persistence/conf/. The default configurations will be populated to the conf/ directory if it's empty.
For example, in order to override the cassandra.yaml configuration file:
You can download the basic cassandra.yaml file like follows
wget https://raw.githubusercontent.com/apache/cassandra/trunk/conf/cassandra.yamlPerform any desired modifications in that file
$ docker run --name cassandra \
-p 7000:7000 \
-e CASSANDRA_TRANSPORT_PORT_NUMBER=7000 \
-v /path/to/cassandra.yaml:/bitnami/cassandra/conf/cassandra.yaml:ro \
-v /your/local/path/bitnami/cassandra:/bitnami \
bitnami/cassandra:latestor using Docker Compose:
version: '2'
services:
cassandra:
image: bitnami/cassandra:latest
environment:
- CASSANDRA_TRANSPORT_PORT_NUMBER=7000
volumes:
- /path/to/cassandra.yaml:/bitnami/cassandra/conf/cassandra.yaml:ro
- /your/local/path/bitnami/cassandra:/bitnamiAfter that, your changes will be taken into account in the server's behaviour. Note that you can override any other Cassandra configuration file, such as rack-dc.properties.
Refer to the Cassandra configuration reference for the complete list of configuration options.
Passing the CASSANDRA_PASSWORD environment variable along with CASSANDRA_PASSWORD_SEEDER=yes when running the image for the first time will set the Cassandra server password to the value of CASSANDRA_PASSWORD.
$ docker run --name cassandra \
-e CASSANDRA_PASSWORD_SEEDER=yes \
-e CASSANDRA_PASSWORD=password123 \
bitnami/cassandra:latestor using Docker Compose:
cassandra:
image: bitnami/cassandra:latest
environment:
- CASSANDRA_PASSWORD_SEEDER=yes
- CASSANDRA_PASSWORD=password123A cluster can easily be setup with the Bitnami Cassandra Docker Image. In case you do not mount custom configuration files, you can use the following environment variables:
CASSANDRA_HOST: Hostname used to configure Cassandra. It can be either an IP or a domain. If left empty, it will be resolved to the machine IP.CASSANDRA_CLUSTER_NAME: Cluster name to configure Cassandra. Defaults: My ClusterCASSANDRA_SEEDS: Hosts that will act as Cassandra seeds. No defaults.CASSANDRA_ENDPOINT_SNITCH: Snitch name (which determines which data centers and racks nodes belong to). Default SimpleSnitchCASSANDRA_PASSWORD_SEEDER: Password seeder will change the Cassandra default credentials at initialization. Only one node should be marked as password seeder. Default: noCASSANDRA_PASSWORD: Cassandra user password. Default: cassandra
Cassandra is a resource-intensive application. Depending on the target system, the initialization can take long. The container has internal timeouts when checking the initialization process. You can use the following environment variables to address that:
CASSANDRA_INIT_MAX_RETRIES: Maximum retries for checking that Cassandra is initialized. Default: 100.CASSANDRA_INIT_SLEEP_TIME: Sleep time (in seconds) between retries for checking that Cassandra is initialized. Default: 5.CASSANDRA_CQL_MAX_RETRIES: Maximum retries for checking that the Cassandra client can access the database in localhost. Default: 20.CASSANDRA_CQL_SLEEP_TIME: Sleep time (in seconds) between retries for checking that the Cassandra client can access the database in localhost. Default: 5.CASSANDRA_PEER_CQL_MAX_RETRIES: Maximum retries for checking that the Cassandra client can access the database located in a peer host. This is used for ensuring that all of the peers are initialized before changing the database credentials. Default: 100.CASSANDRA_PEER_CQL_SLEEP_TIME: Sleep time (in seconds) between retries for checking that the Cassandra client can access the database in a peer host. Default: 5.
$ docker network create cassandra_network$ docker run --name cassandra-node1 \
--net=cassandra_network \
-p 9042:9042 \
-e CASSANDRA_CLUSTER_NAME=cassandra-cluster \
-e CASSANDRA_SEEDS=cassandra-node1,cassandra-node2 \
-e CASSANDRA_PASSWORD_SEEDER=yes \
-e CASSANDRA_PASSWORD=mypassword \
bitnami/cassandra:latestIn the above command the container is added to a cluster named cassandra-cluster using the CASSANDRA_CLUSTER_NAME. The CASSANDRA_CLUSTER_HOSTS parameter set the name of the nodes that set the cluster so we will need to launch other container for the second node. Finally the CASSANDRA_NODE_NAME parameter allows to indicate a known name for the node, otherwise cassandra will generate a randon one.
$ docker run --name cassandra-node2 \
--net=cassandra_network \
-e CASSANDRA_CLUSTER_NAME=cassandra-cluster \
-e CASSANDRA_SEEDS=cassandra-node1,cassandra-node2 \
-e CASSANDRA_PASSWORD=mypassword \
bitnami/cassandra:latestIn the above command a new cassandra node is being added to the cassandra cluster indicated by CASSANDRA_CLUSTER_NAME.
You now have a two node Cassandra cluster up and running which can be scaled by adding/removing nodes.
With Docker Compose the cluster configuration can be setup using:
version: '2'
services:
cassandra-node1:
image: bitnami/cassandra:latest
environment:
- CASSANDRA_CLUSTER_NAME=cassandra-cluster
- CASSANDRA_SEEDS=cassandra-node1,cassandra-node2
- CASSANDRA_PASSWORD_SEEDER=yes
- CASSANDRA_PASSWORD=password123
cassandra-node2:
image: bitnami/cassandra:latest
environment:
- CASSANDRA_CLUSTER_NAME=cassandra-cluster
- CASSANDRA_SEEDS=cassandra-node1,cassandra-node2
- CASSANDRA_PASSWORD=password123When the container is executed for the first time, it will execute the files with extensions .sh, .cql or .cql.gz located at /docker-entrypoint-initdb.d in sort'ed order by filename. This behavior can be skipped by setting the environment variable CASSANDRA_IGNORE_INITDB_SCRIPTS to a value other than yes or true.
In order to have your custom files inside the docker image you can mount them as a volume.
$ docker run --name cassandra \
-v /path/to/init-scripts:/docker-entrypoint-initdb.d \
-v /path/to/cassandra-persistence:/bitnami
bitnami/cassandra:latestOr with docker-compose
cassandra:
image: bitnami/cassandra:latest
volumes:
- /path/to/init-scripts:/docker-entrypoint-initdb.d
- /path/to/cassandra-persistence:/bitnamiThe image looks for configurations in /bitnami/cassandra/conf/. As mentioned in Persisting your application you can mount a volume at /bitnami and copy/edit the configurations in the /path/to/cassandra-persistence/cassandra/conf/. The default configurations will be populated to the conf/ directory if it's empty.
Run the Cassandra image, mounting a directory from your host.
$ docker run --name cassandra \
-v /path/to/cassandra-persistence:/bitnami \
bitnami/cassandra:latestor using Docker Compose:
cassandra:
image: bitnami/cassandra:latest
volumes:
- /path/to/cassandra-persistence:/bitnamiEdit the configuration on your host using your favorite editor.
vi /path/to/cassandra-persistence/cassandra/conf/cassandra.yamlAfter changing the configuration, restart your Cassandra container for changes to take effect.
$ docker restart cassandraor using Docker Compose:
$ docker-compose restart cassandraRefer to the configuration manual for the complete list of configuration options.
The Bitnami Cassandra Docker image allows configuring TLS encryption between nodes and between server-client. This is done by mounting in /bitnami/cassandra/secrets two files:
keystore: File with the server keystoretruststore: File with the server truststore
Apart from that, the following environment variables must be set:
CASSANDRA_KEYSTORE_PASSWORD: Password for accessing the keystore.CASSANDRA_TRUSTSTORE_PASSWORD: Password for accessing the truststore.CASSANDRA_INTERNODE_ENCRYPTION: Sets the type of encryption between nodes. The default value isnone. Can be set toall,none,dcorrack.CASSANDRA_CLIENT_ENCRYPTION: Enables client-server encryption. The default value isfalse.
The Bitnami Cassandra Docker image sends the container logs to the stdout. To view the logs:
$ docker logs cassandraor using Docker Compose:
$ docker-compose logs cassandraYou can configure the containers logging driver using the --log-driver option if you wish to consume the container logs differently. In the default configuration docker uses the json-file driver.
Bitnami provides up-to-date versions of Cassandra, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.
$ docker pull bitnami/cassandra:latestor if you're using Docker Compose, update the value of the image property to
bitnami/cassandra:latest.
Stop the currently running container using the command
$ docker stop cassandraor using Docker Compose:
$ docker-compose stop cassandraNext, take a snapshot of the persistent volume /path/to/cassandra-persistence using:
$ rsync -a /path/to/cassandra-persistence /path/to/cassandra-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)$ docker rm -v cassandraor using Docker Compose:
$ docker-compose rm -v cassandraRe-create your container from the new image.
$ docker run --name cassandra bitnami/cassandra:latestor using Docker Compose:
$ docker-compose up cassandra- Decrease the size of the container. The configuration logic is now based on Bash scripts in the
rootfs/folder.
-The Cassandra container now adds the possibility to inject custom initialization scripts by mounting cql and sh files in /docker-entrypoint-initdb.d. See this section for more information.
- The Cassandra container has been migrated to a non-root user approach. Previously the container ran as the
rootuser and the Cassandra daemon was started as thecassandrauser. From now on, both the container and the Cassandra daemon run as user1001. As a consequence, the data directory must be writable by that user. You can revert this behavior by changingUSER 1001toUSER rootin the Dockerfile.
We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.
If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:
- Host OS and version
- Docker version (
docker version) - Output of
docker info - Version of this container (
echo $BITNAMI_IMAGE_VERSIONinside the container) - The command you used to run the container, and any relevant output you saw (masking any sensitive information)
Copyright (c) 2016-2020 Bitnami
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.