public_git
/
bitnami-containers
mirror of https://github.com/bitnami/containers.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

[bitnami/scylladb] Release 2026.1.2-debian-12-r0 (#92767) 

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot 2026-05-03 18:16:59 +02:00 committed by GitHub
parent ab515daeac
commit 28bdf1ba3a
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 9 additions and 129 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
bitnami/scylladb/2026.1/debian-12/Dockerfile
View File

@ -8,13 +8,13 @@ ARG JAVA_EXTRA_SECURITY_DIR="/bitnami/java/extra-security"
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-04-08T22:00:15Z" \
org.opencontainers.image.created="2026-05-03T16:03:23Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/scylladb/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/scylladb" \
org.opencontainers.image.title="scylladb" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="2026.1.1"
org.opencontainers.image.version="2026.1.2"
ENV HOME="/" \
OS_ARCH="${TARGETARCH:-amd64}" \
@ -24,14 +24,14 @@ ENV HOME="/" \
COPY prebuildfs /
SHELL ["/bin/bash", "-o", "errexit", "-o", "nounset", "-o", "pipefail", "-c"]
# Install required system packages and dependencies
RUN install_packages ca-certificates curl libatomic1 libblkid1 libbz2-1.0 libcom-err2 libcrypt1 libffi8 libgcc-s1 libgcrypt20 libgmp10 libgnutls30 libgpg-error0 libgssapi-krb5-2 libhogweed6 libidn2-0 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblz4-1 liblzma5 libmount1 libmpfr6 libncursesw6 libnettle8 libnsl2 libp11-kit0 libpcre2-8-0 libreadline8 libselinux1 libsmartcols1 libsqlite3-0 libssl3 libstdc++6 libsystemd0 libtasn1-6 libtinfo6 libtirpc3 libudev1 libunistring2 libxxhash0 libzstd1 procps rsyslog zlib1g
RUN install_packages ca-certificates curl libatomic1 libblkid1 libbz2-1.0 libcom-err2 libcrypt1 libffi8 libgcc-s1 libgmp10 libgnutls30 libgssapi-krb5-2 libhogweed6 libidn2-0 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblz4-1 liblzma5 libmount1 libmpfr6 libncursesw6 libnettle8 libnsl2 libp11-kit0 libpcre2-8-0 libreadline8 libselinux1 libsmartcols1 libsqlite3-0 libssl3 libstdc++6 libsystemd0 libtasn1-6 libtinfo6 libtirpc3 libudev1 libunistring2 libxxhash0 libzstd1 procps rsyslog zlib1g
RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"python-3.12.13-3-linux-${OS_ARCH}-debian-12" \
"jre-11.0.30-9-1-linux-${OS_ARCH}-debian-12" \
"scylladb-2026.1.1-0-linux-${OS_ARCH}-debian-12" \
"python-3.12.13-7-linux-${OS_ARCH}-debian-12" \
"jre-11.0.31-11-0-linux-${OS_ARCH}-debian-12" \
"scylladb-2026.1.2-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@ -51,9 +51,9 @@ RUN uninstall_packages curl
COPY rootfs /
RUN /opt/bitnami/scripts/scylladb/postunpack.sh
RUN /opt/bitnami/scripts/java/postunpack.sh
ENV APP_VERSION="2026.1.1" \
ENV APP_VERSION="2026.1.2" \
BITNAMI_APP_NAME="scylladb" \
IMAGE_REVISION="1" \
IMAGE_REVISION="0" \
JAVA_HOME="/opt/bitnami/java" \
PATH="/opt/bitnami/python/bin:/opt/bitnami/java/bin:/opt/bitnami/scylladb/bin:/opt/bitnami/scylladb/sbin:/opt/bitnami/scylladb/python3/bin:/opt/bitnami/supervisor/bin:/opt/bitnami/scylladb/share/cassandra/bin:$PATH"

122
bitnami/scylladb/README.md
View File

@ -46,10 +46,6 @@ Learn more about the Bitnami tagging policy and the difference between rolling t
The Bitnami ScyllaDB Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers.
## Using `docker-compose.yaml`
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/scylladb).
## Persisting your application
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.
@ -73,75 +69,6 @@ scylladb:
> **NOTE** As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
## Connecting to other containers
Using [Docker container networking](https://docs.docker.com/engine/userguide/networking/), an ScyllaDB 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.
### Using the Command Line
In this example, we will create an ScyllaDB client instance that will connect to the server instance that is running on the same docker network as the client.
#### Step 1: Create a network
```console
docker network create app-tier --driver bridge
```
#### Step 2: Launch the ScyllaDB server instance
Use the `--network app-tier` argument to the `docker run` command to attach the ScyllaDB container to the `app-tier` network.
```console
docker run -d --name scylladb-server \
--network app-tier \
bitnami/scylladb:latest
```
#### Step 3: Launch your ScyllaDB client instance
Finally we create a new container instance to launch the ScyllaDB client and connect to the server created in the previous step:
```console
docker run -it --rm \
--network app-tier \
bitnami/scylladb:latest cqlsh --username scylladb --password scylladb scylladb-server
```
### 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 ScyllaDB server from your own custom application image which is identified in the following snippet by the service name `myapp`.
```yaml
version: '2'
networks:
app-tier:
driver: bridge
services:
scylladb:
image: bitnami/scylladb:latest
networks:
- app-tier
myapp:
image: YOUR_APPLICATION_IMAGE
networks:
- app-tier
```
> **IMPORTANT**:
>
> 1. Please update the **YOUR_APPLICATION_IMAGE** placeholder in the above snippet with your application image
> 2. In your application container, use the hostname `scylladb` to connect to the ScyllaDB server
Launch the containers using:
```console
docker-compose up -d
```
## Configuration
The following section describes the supported environment variables
@ -254,26 +181,6 @@ For example, use `SCYLLADB_CFG_RACKDC_PREFER_LOCAL=true` in order to configure `
**NOTE:** Environment variables will be omitted when mounting a configuration file
When you start the scylladb 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:
```yaml
scylladb:
image: bitnami/scylladb:latest
environment:
- SCYLLADB_TRANSPORT_PORT_NUMBER=7000
```
- For manual execution add a `-e` option with each variable and value:
```console
$ docker run --name scylladb -d -p 7000:7000 --network=scylladb_network \
-e SCYLLADB_TRANSPORT_PORT_NUMBER=7000 \
-v /your/local/path/bitnami/scylladb:/bitnami \
bitnami/scylladb
```
### Setting the server password on first run
Passing the `SCYLLADB_PASSWORD` environment variable along with `SCYLLADB_PASSWORD_SEEDER=yes` when running the image for the first time will set the ScyllaDB server password to the value of `SCYLLADB_PASSWORD`.
@ -389,15 +296,6 @@ docker run --name scylladb \
bitnami/scylladb:latest
```
or using Docker Compose:
```yaml
scylladb:
image: bitnami/scylladb:latest
volumes:
- /path/to/scylladb-persistence:/bitnami
```
#### Step 2: Edit the configuration
Edit the configuration on your host using your favorite editor.
@ -414,12 +312,6 @@ After changing the configuration, restart your ScyllaDB container for changes to
docker restart scylladb
```
or using Docker Compose:
```console
docker-compose restart scylladb
```
Refer to the [configuration](http://docs.datastax.com/en/scylladb/3.x/scylladb/configuration/configTOC.html) manual for the complete list of configuration options.
### FIPS configuration in Bitnami Secure Images
@ -445,19 +337,7 @@ Apart from that, the following environment variables must be set:
## Logging
The Bitnami ScyllaDB Docker image sends the container logs to the `stdout`. To view the logs:
```console
docker logs scylladb
```
or using Docker Compose:
```console
docker-compose logs scylladb
```
You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
The Bitnami ScyllaDB Docker image sends the container logs to the `stdout`. You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
## License