[bitnami/logstash] Release 9.3.4-debian-12-r0 (#92711)

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot 2026-04-30 20:10:05 +02:00 committed by GitHub
parent f22a234291
commit af97dd2fcb
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 15 additions and 20 deletions

View File

@ -9,13 +9,13 @@ ARG LOGSTASH_PLUGINS
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-04-08T20:08:33Z" \
org.opencontainers.image.created="2026-04-30T17:44:20Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/logstash/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/logstash" \
org.opencontainers.image.title="logstash" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="9.3.3"
org.opencontainers.image.version="9.3.4"
ENV HOME="/" \
OS_ARCH="${TARGETARCH:-amd64}" \
@ -30,9 +30,9 @@ 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=( \
"yq-4.52.5-1-linux-${OS_ARCH}-debian-12" \
"java-17.0.18-10-1-linux-${OS_ARCH}-debian-12" \
"logstash-9.3.3-0-linux-${OS_ARCH}-debian-12" \
"yq-4.53.2-0-linux-${OS_ARCH}-debian-12" \
"java-17.0.19-11-0-linux-${OS_ARCH}-debian-12" \
"logstash-9.3.4-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@ -52,7 +52,7 @@ RUN uninstall_packages curl
COPY rootfs /
RUN /opt/bitnami/scripts/java/postunpack.sh
RUN /opt/bitnami/scripts/logstash/postunpack.sh
ENV APP_VERSION="9.3.3" \
ENV APP_VERSION="9.3.4" \
BITNAMI_APP_NAME="logstash" \
IMAGE_REVISION="0" \
JAVA_HOME="/opt/bitnami/java" \

View File

@ -11,6 +11,14 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
docker run --name logstash bitnami/logstash:latest
```
## Using `docker-compose.yml`
The docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/).
[https://github.com/bitnami/containers/tree/main/bitnami/logstash/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/logstash/docker-compose.yml)
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/logstash).
## Why use Bitnami Secure Images?
Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images?
@ -44,10 +52,6 @@ Learn more about the Bitnami tagging policy and the difference between rolling t
The Bitnami Logstash 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/logstash).
## Persisting your application
If you remove the container all your data 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.
@ -193,16 +197,7 @@ The Bitnami Logstash Docker image from the [Bitnami Secure Images](https://go-vm
## Logging
The Bitnami Logstash Docker image sends the container logs to `stdout`. To view the logs:
```console
docker logs logstash
```
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.
Additionally, in case you'd like to modify Logstash logging configuration, it can be done by overwriting the file `/opt/bitnami/logstash/config/log4j2.properties`.
The syntax of this file can be found in Logstash [logging documentation](https://www.elastic.co/guide/en/logstash/current/logging.html).
The Bitnami Logstash 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.
## Notable Changes