Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-02-20 14:57:23 +08:00
Code Issues Packages Projects Releases Wiki Activity

4.0.3-debian-10-r60 release

Browse Source
This commit is contained in:
Bitnami Bot
2022-04-20 13:44:05 +00:00
committed by Bitnami Containers
parent 4f50eef6d9
commit 05af042aec
1 changed files with 1 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
bitnami/cassandra/README.md
View File

@@ -32,9 +32,6 @@ You can find the default credentials and available configuration options in the
* All Bitnami images available in Docker Hub are signed with [Docker Content Trust (DCT)](https://docs.docker.com/engine/security/trust/content_trust/). You can use `DOCKER_CONTENT_TRUST=1` to verify the integrity of the images.
* Bitnami container images are released daily with the latest distribution packages available.
> This [CVE scan report](https://quay.io/repository/bitnami/cassandra?tab=tags) 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.
## Why use a non-root container?
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](https://docs.bitnami.com/tutorials/work-with-non-root-containers/).
@@ -50,7 +47,7 @@ Bitnami containers can be used with [Kubeapps](https://kubeapps.com/) for deploy
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/tutorials/understand-rolling-tags-containers/).
* [`4.0`, `4.0-debian-10`, `4.0.3`, `4.0.3-debian-10-r59`, `latest` (4.0/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-cassandra/blob/4.0.3-debian-10-r59/4.0/debian-10/Dockerfile)
* [`4.0`, `4.0-debian-10`, `4.0.3`, `4.0.3-debian-10-r60`, `latest` (4.0/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-cassandra/blob/4.0.3-debian-10-r60/4.0/debian-10/Dockerfile)
* [`3.11`, `3.11-debian-10`, `3.11.12`, `3.11.12-debian-10-r65` (3.11/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-cassandra/blob/3.11.12-debian-10-r65/3.11/debian-10/Dockerfile)
* [`3.0`, `3.0-debian-10`, `3.0.26`, `3.0.26-debian-10-r64` (3.0/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-cassandra/blob/3.0.26-debian-10-r64/3.0/debian-10/Dockerfile)
@@ -277,7 +274,6 @@ services:
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`.