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

[bitnami/fluent-bit] Release 5.0.3-debian-12-r0 (#92462)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-04-14 21:22:36 +02:00
committed by GitHub
parent 66a7e2b8e6
commit b637a8b973
2 changed files with 14 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/fluent-bit/5.0/debian-12/Dockerfile
+5 -5
View File
@@ -7,13 +7,13 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith"
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-04-14T08:15:22Z" \
org.opencontainers.image.created="2026-04-14T19:12:02Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/fluent-bit/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/fluent-bit" \
org.opencontainers.image.title="fluent-bit" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="5.0.2"
org.opencontainers.image.version="5.0.3"
ENV HOME="/" \
OS_ARCH="${TARGETARCH:-amd64}" \
@@ -28,7 +28,7 @@ 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=( \
"fluent-bit-5.0.2-2-linux-${OS_ARCH}-debian-12" \
"fluent-bit-5.0.3-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -46,9 +46,9 @@ RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
RUN chown -R 1001:1001 /opt/bitnami/fluent-bit
RUN uninstall_packages curl
ENV APP_VERSION="5.0.2" \
ENV APP_VERSION="5.0.3" \
BITNAMI_APP_NAME="fluent-bit" \
IMAGE_REVISION="3" \
IMAGE_REVISION="0" \
PATH="/opt/bitnami/fluent-bit/bin:$PATH"
EXPOSE 2020
bitnami/fluent-bit/README.md
+9 -70
View File
@@ -11,6 +11,14 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
docker run --name fluent-bit bitnami/fluent-bit: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/fluent-bit/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/fluent-bit/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/fluent-bit).
## 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?
@@ -40,69 +48,6 @@ Learn more about the Bitnami tagging policy and the difference between rolling t
The Bitnami Fluent Bit 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/fluent-bit).
## 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
#### Step 1: Create a network
```console
docker network create fluent-bit-network --driver bridge
```
#### Step 2: Launch the Fluent Bit container within your network
Use the `--network <NETWORK>` argument to the `docker run` command to attach the container to the `fluent-bit-network` network.
```console
docker run --name fluent-bit-node1 --network fluent-bit-network bitnami/fluent-bit:latest
```
#### Step 3: Run another container
We can launch another container 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.
### 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 Fluent Bit log processor 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:
fluent-bit:
image: bitnami/fluent-bit: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 `fluent-bit` to connect to the Fluent Bit log processor
Launch the containers using:
```console
docker-compose up -d
```
## Configuration
Fluent Bit is flexible enough to be configured either from the command line or through a configuration file. For production environments, Fluent Bit strongly recommends to use the configuration file approach.
@@ -123,13 +68,7 @@ Fluent Bit supports multiple extensions via plugins.
## Logging
The Bitnami fluent-bit Docker image sends the container logs to the `stdout`. To view the logs:
```console
docker logs fluent-bit
```
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 Fluent Bit 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