[bitnami/cassandra] Release 4.0.8-debian-11-r1 (#24202)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot 2023-02-17 15:39:21 +01:00 committed by GitHub
parent 619d01ca7c
commit 80ae3fe2f5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 68 additions and 65 deletions

View File

@ -3,11 +3,11 @@ FROM docker.io/bitnami/minideb:bullseye
ARG JAVA_EXTRA_SECURITY_DIR="/bitnami/java/extra-security"
ARG TARGETARCH
LABEL org.opencontainers.image.authors="https://bitnami.com/contact" \
org.opencontainers.image.description="Application packaged by Bitnami" \
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2023-02-17T14:06:07Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="4.0.8-debian-11-r0" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/cassandra" \
org.opencontainers.image.ref.name="4.0.8-debian-11-r1" \
org.opencontainers.image.title="cassandra" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="4.0.8"
@ -23,11 +23,11 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
RUN install_packages ca-certificates curl libbz2-1.0 libcom-err2 libcrypt1 libffi7 libgcc-s1 libgssapi-krb5-2 libjemalloc2 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblzma5 libncursesw6 libnsl2 libreadline8 libsqlite3-0 libssl1.1 libtinfo6 libtirpc3 procps zlib1g
RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
COMPONENTS=( \
"python-3.9.16-3-linux-${OS_ARCH}-debian-11" \
"java-1.8.362-0-linux-${OS_ARCH}-debian-11" \
"gosu-1.16.0-1-linux-${OS_ARCH}-debian-11" \
"yq-4.30.8-1-linux-${OS_ARCH}-debian-11" \
"cassandra-4.0.8-0-linux-${OS_ARCH}-debian-11" \
"python-3.9.16-4-linux-${OS_ARCH}-debian-11" \
"java-1.8.362-1-linux-${OS_ARCH}-debian-11" \
"gosu-1.16.0-2-linux-${OS_ARCH}-debian-11" \
"yq-4.30.8-2-linux-${OS_ARCH}-debian-11" \
"cassandra-4.0.8-1-linux-${OS_ARCH}-debian-11" \
) && \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \

View File

@ -1,37 +1,37 @@
{
"cassandra": {
"arch": "amd64",
"digest": "ee74352a04bf97e41fc11fc0009e92e2b9d3aa40ee846bdb0dabfb52744f3b29",
"digest": "e308aab6256bf49eaea4302f43b676bd2f3a3912ab48e72f7112a7ba4c4f1e01",
"distro": "debian-11",
"type": "NAMI",
"version": "4.0.8-0"
"version": "4.0.8-1"
},
"gosu": {
"arch": "amd64",
"digest": "9ab9654690d90d3c49ff66fb1eb286487e318adc899d036bc45922f6b176865b",
"digest": "f6056076afb745fd7d9d87d20f71e7248d63330352cf5ae0be2130b7f44a8cfa",
"distro": "debian-11",
"type": "NAMI",
"version": "1.16.0-1"
"version": "1.16.0-2"
},
"java": {
"arch": "amd64",
"digest": "19976426bb1d50974588dbe1fece1d8e54dc9932d15dd6b81b37fdf2c8307495",
"digest": "5bd5372669617e425c32344e8ce1558d9402474acf2c7ed8ccd54c3fbcca7ce1",
"distro": "debian-11",
"type": "NAMI",
"version": "1.8.362-0"
"version": "1.8.362-1"
},
"python": {
"arch": "amd64",
"digest": "dc98177aa6bb38b1df12fbc42b826ef1ced23b3620355832f905454a7c67b617",
"digest": "3ca3cf3d15f16edd34757f892175aed86e3d95b1919425218c831cb8a29beea0",
"distro": "debian-11",
"type": "NAMI",
"version": "3.9.16-3"
"version": "3.9.16-4"
},
"yq": {
"arch": "amd64",
"digest": "33fec06619aa3c1f7ea3c2516bf36f79af01354972ff06998ca6fe1d65078998",
"digest": "2fcd60b9977991e83f7066cf6da2c319b21483cdc67597625af37fa753534faf",
"distro": "debian-11",
"type": "NAMI",
"version": "4.30.8-1"
"version": "4.30.8-2"
}
}

View File

@ -131,7 +131,7 @@ docker run -it --rm \
bitnami/cassandra:latest cqlsh --username cassandra --password cassandra cassandra-server
```
### Using Docker Compose
### Using a Docker Compose file
When 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 Apache Cassandra server from your own custom application image which is identified in the following snippet by the service name `myapp`.
@ -182,7 +182,7 @@ cassandra:
* For manual execution add a `-e` option with each variable and value:
```console
docker run --name cassandra -d -p 7000:7000 --network=cassandra_network \
$ 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/cassandra
@ -232,50 +232,6 @@ cassandra:
...
```
### Configuration file
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:
#### Step 1: Write your custom `cassandra.yaml` file
You can download the basic cassandra.yaml file like follows
```console
wget https://raw.githubusercontent.com/apache/cassandra/trunk/conf/cassandra.yaml
```
Perform any desired modifications in that file
#### Step 2: Run the Apache Cassandra image with the designed volume attached
```console
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:latest
```
or using Docker Compose:
```yaml
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:/bitnami
```
After that, your changes will be taken into account in the server's behaviour. Note that you can override any other Apache Cassandra configuration file, such as `rack-dc.properties`.
### Setting the server password on first run
Passing the `CASSANDRA_PASSWORD` environment variable along with `CASSANDRA_PASSWORD_SEEDER=yes` when running the image for the first time will set the Apache Cassandra server password to the value of `CASSANDRA_PASSWORD`.
@ -397,6 +353,53 @@ cassandra:
- /path/to/cassandra-persistence:/bitnami
```
### Configuration file
The image looks for configurations in `/bitnami/cassandra/conf/`. As mentioned in [Persisting your application](#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.
#### Step 1: Run the Apache Cassandra image
Run the Apache Cassandra image, mounting a directory from your host.
```console
docker run --name cassandra \
-v /path/to/cassandra-persistence:/bitnami \
bitnami/cassandra:latest
```
or using Docker Compose:
```yaml
cassandra:
image: bitnami/cassandra:latest
volumes:
- /path/to/cassandra-persistence:/bitnami
```
#### Step 2: Edit the configuration
Edit the configuration on your host using your favorite editor.
```console
vi /path/to/cassandra-persistence/cassandra/conf/cassandra.yaml
```
#### Step 3: Restart Apache Cassandra
After changing the configuration, restart your Apache Cassandra container for changes to take effect.
```console
docker restart cassandra
```
or using Docker Compose:
```console
docker-compose restart cassandra
```
Refer to the [configuration](http://docs.datastax.com/en/cassandra/3.x/cassandra/configuration/configTOC.html) manual for the complete list of configuration options.
## TLS Encryption
The Bitnami Apache Cassandra Docker image allows configuring TLS encryption between nodes and between server-client. This is done by mounting in `/bitnami/cassandra/secrets` two files: