public_git/bitnami-containers
1
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-10-18 16:02:49 +02:00
Code Issues Projects Releases Wiki Activity

[bitnami/logstash] Release 9.3.1-debian-12-r0 (#91136)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-02-26 22:29:33 +01:00
committed by GitHub
parent 997e5cc5fe
commit 4fbdc28c6b
2 changed files with 30 additions and 110 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/logstash/9.3/debian-12/Dockerfile
+5 -5
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-02-19T02:51:38Z" \
org.opencontainers.image.created="2026-02-26T20:57:56Z" \
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.0"
org.opencontainers.image.version="9.3.1"
ENV HOME="/" \
OS_ARCH="${TARGETARCH:-amd64}" \
@@ -32,7 +32,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
COMPONENTS=( \
"yq-4.52.4-0-linux-${OS_ARCH}-debian-12" \
"java-17.0.18-10-1-linux-${OS_ARCH}-debian-12" \
"logstash-9.3.0-1-linux-${OS_ARCH}-debian-12" \
"logstash-9.3.1-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -52,9 +52,9 @@ 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.0" \
ENV APP_VERSION="9.3.1" \
BITNAMI_APP_NAME="logstash" \
IMAGE_REVISION="2" \
IMAGE_REVISION="0" \
JAVA_HOME="/opt/bitnami/java" \
PATH="/opt/bitnami/common/bin:/opt/bitnami/java/bin:/opt/bitnami/logstash/bin:$PATH"
bitnami/logstash/README.md
+25 -105
View File
@@ -1,19 +1,17 @@
# Bitnami Secure Image for Logstash
## What is Logstash?
> Logstash is an open source data processing engine. It ingests data from multiple sources, processes it, and sends the output to final destination in real-time. It is a core component of the ELK stack.
[Overview of Logstash](https://logstash.net)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
## <a id="tl-dr"></a> TL;DR
```console
docker run --name logstash bitnami/logstash:latest
```
## Why use Bitnami Secure Images?
## <a id="why-use-bitnami-secure-images"></a> 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?
@@ -30,19 +28,19 @@ Each image comes with valuable security metadata. You can view the metadata in [
If you are looking for our previous generation of images based on Debian Linux, please see the [Bitnami Legacy registry](https://hub.docker.com/u/bitnamilegacy).
## How to deploy Logstash in Kubernetes?
## <a id="how-to-deploy-logstash-in-kubernetes?"></a> How to deploy Logstash in Kubernetes?
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 Logstash Chart GitHub repository](https://github.com/bitnami/charts/tree/main/bitnami/logstash).
## Why use a non-root container?
## <a id="why-non-root"></a> 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://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-work-with-non-root-containers-index.html).
## Supported tags and respective `Dockerfile` links
## <a id="supported-tags"></a> Supported tags and respective `Dockerfile` links
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html).
## Get this image
## <a id="get-this-image"></a> Get this image
The recommended way to get the Bitnami Logstash Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/logstash).
@@ -64,65 +62,27 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .
```
## Persisting your application
## <a id="using-`docker-compose.yaml`"></a> 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).
## <a id="persisting-your-application"></a> 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.
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.
```console
docker run \
-v /path/to/logstash-persistence:/bitnami \
bitnami/logstash:latest
```
> **NOTE** As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
You can also do this with a minor change to the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/logstash/docker-compose.yml) file present in this repository:
```yaml
logstash:
...
volumes:
- /path/to/logstash-persistence:/bitnami
...
```
> 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
## <a id="connecting-to-other-containers"></a> Connecting to other containers
Using [Docker container networking](https://docs.docker.com/engine/userguide/networking/), a different server running inside a container can easily be accessed by your application containers and vice-versa.
Containers attached to the same network can communicate with each other using the container name as the hostname.
### Using the Command Line
### <a id="environment-variables"></a> Environment variables
#### Step 1: Create a network
```console
docker network create logstash-network --driver bridge
```
#### Step 2: Launch the Logstash container within your network
Use the `--network <NETWORK>` argument to the `docker run` command to attach the container to the `logstash-network` network.
```console
docker run --name logstash-node1 --network logstash-network bitnami/logstash:latest
```
#### Step 3: Run another containers
We can launch another containers using the same flag (`--network NETWORK`) in the `docker run` command. If you also set a name to your container, you will be able to use it as hostname in your network.
## Configuration
By default, this container provides a very basic configuration for Logstash, that listen http on port 8080 and writes to stdout.
```console
docker run -d -p 8080:8080 bitnami/logstash:latest
```
### Environment variables
The following tables list the main variables you can set.
#### Customizable environment variables
@@ -176,7 +136,7 @@ docker run -d -p 8080:8080 bitnami/logstash:latest
| `JAVA_HOME` | Java installation folder. | `${BITNAMI_ROOT_DIR}/java` |
| `LS_JAVA_OPTS` | Logstash supported Java options. | `${LS_JAVA_OPTS:-} ${JAVA_TOOL_OPTIONS:-}` |
### Using a configuration string
### <a id="using-a-configuration-string"></a> Using a configuration string
For simple configurations, you specify it using the `LOGSTASH_CONF_STRING` environment variable:
@@ -184,7 +144,7 @@ For simple configurations, you specify it using the `LOGSTASH_CONF_STRING` envir
docker run --env LOGSTASH_CONF_STRING="input {file {path => \"/tmp/logstash_input\"}} output {file {path => \"/tmp/logstash_output\"}}" bitnami/logstash:latest
```
### Using a configuration file
### <a id="using-a-configuration-file"></a> Using a configuration file
You can override the default configuration for Logstash by mounting your own configuration files on directory `/bitnami/logstash/pipeline`. You will need to indicate the file holding the pipeline definition by setting the `LOGSTASH_PIPELINE_CONF_FILENAME` environment variable.
@@ -192,7 +152,7 @@ You can override the default configuration for Logstash by mounting your own con
docker run -d --env LOGSTASH_PIPELINE_CONF_FILENAME=my_config.conf -v /path/to/custom-conf-directory:/bitnami/logstash/pipeline bitnami/logstash:latest
```
### Additional command line options
### <a id="additional-command-line-options"></a> Additional command line options
In case you want to add extra flags to the Logstash command, use the `LOGSTASH_EXTRA_FLAGS` variable. Example:
@@ -200,7 +160,7 @@ In case you want to add extra flags to the Logstash command, use the `LOGSTASH_E
docker run -d --env LOGSTASH_EXTRA_FLAGS="-w 4 -b 4096" bitnami/logstash:latest
```
### Using multiple pipelines
### <a id="using-multiple-pipelines"></a> Using multiple pipelines
You can use [multiple pipelines](https://www.elastic.co/guide/en/logstash/master/multiple-pipelines.html) by setting the `LOGSTASH_ENABLE_MULTIPLE_PIPELINES` environment variable to `true`.
@@ -210,7 +170,7 @@ In that case, you should place your `pipelines.yml` file in the mounted volume (
docker run -d --env LOGSTASH_ENABLE_MULTIPLE_PIPELINES=true -v /path/to/custom-conf-directory:/bitnami/logstash/config bitnami/logstash:latest
```
### Exposing Logstash API
### <a id="exposing-api"></a> Exposing Logstash API
You can expose the Logstash API by setting the environment variable `LOGSTASH_EXPOSE_API`, you can also change the default port by using `LOGSTASH_API_PORT_NUMBER`.
@@ -218,7 +178,7 @@ You can expose the Logstash API by setting the environment variable `LOGSTASH_EX
docker run -d --env LOGSTASH_EXPOSE_API=yes --env LOGSTASH_API_PORT_NUMBER=9090 -p 9090:9090 bitnami/logstash:latest
```
### Plugins
### <a id="plugins"></a> Plugins
You can add extra plugins by setting the `LOGSTASH_PLUGINS` environment variable. To specify multiple plugins, separate them by spaces, commas or semicolons. When the container is initialized it will install all of the specified plugins before starting Logstash.
@@ -242,13 +202,13 @@ docker build --build-arg LOGSTASH_PLUGINS=<plugin1,plugin2,...> -t bitnami/logst
The command above will build the image providing this GitHub repository as build context, and will pass the list of plugins to install to the build logic.
### FIPS configuration in Bitnami Secure Images
### <a id="fips-configuration"></a> FIPS configuration in Bitnami Secure Images
The Bitnami Logstash Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:
- `OPENSSL_FIPS`: whether OpenSSL runs in FIPS mode or not. `yes` (default), `no`.
## Logging
## <a id="logging"></a> Logging
The Bitnami Logstash Docker image sends the container logs to `stdout`. To view the logs:
@@ -261,53 +221,13 @@ You can configure the containers [logging driver](https://docs.docker.com/engine
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).
## Maintenance
### Upgrade this image
Bitnami provides up-to-date versions of Logstash, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.
#### Step 1: Get the updated image
```console
docker pull bitnami/logstash:latest
```
#### Step 2: Stop the running container
Stop the currently running container using the command
```console
docker stop logstash
```
#### Step 3: Remove the currently running container
```console
docker rm -v logstash
```
#### Step 4: Run the new image
Re-create your container from the new image.
```console
docker run --name logstash bitnami/logstash:latest
```
## Notable Changes
## <a id="notable-changes"></a> Notable Changes
### 7.15.2-debian-10-r12
- Pipeline configuration files (i.e. `default_config.conf`) are being added into the `/opt/bitnami/logstash/pipeline` directory, instead of `/opt/bitnami/logstash/config`. Subsequently, `LOGSTASH_CONF_FILENAME` was renamed to `LOGSTASH_PIPELINE_CONF_FILENAME`, and `LOGSTASH_CONF_STRING` was renamed to `LOGSTASH_PIPELINE_CONF_STRING`.
## 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).
If you detect any issue in the `docker-compose.yaml` file, feel free to report it or contribute with a fix by following our [Contributing Guidelines](https://github.com/bitnami/containers/blob/main/CONTRIBUTING.md).
## License
## <a id="license"></a> License
Copyright &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.