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

[bitnami/kibana] Release 9.3.1-debian-12-r0 (#91135)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-02-26 22:03:15 +01:00
committed by GitHub
parent f67f9021a0
commit 997e5cc5fe
2 changed files with 31 additions and 73 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/kibana/9.3/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-02-19T02:18:45Z" \
org.opencontainers.image.created="2026-02-26T20:13:56Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/kibana/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/kibana" \
org.opencontainers.image.title="kibana" \
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}" \
@@ -30,7 +30,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"yq-4.52.4-0-linux-${OS_ARCH}-debian-12" \
"kibana-9.3.0-0-linux-${OS_ARCH}-debian-12" \
"kibana-9.3.1-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -48,9 +48,9 @@ RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
COPY rootfs /
RUN /opt/bitnami/scripts/kibana/postunpack.sh
ENV APP_VERSION="9.3.0" \
ENV APP_VERSION="9.3.1" \
BITNAMI_APP_NAME="kibana" \
IMAGE_REVISION="1"
IMAGE_REVISION="0"
EXPOSE 5601
bitnami/kibana/README.md
+26 -68
View File
@@ -1,21 +1,19 @@
# Bitnami Secure Image for Kibana
## What is Kibana?
> Kibana is an open source, browser based analytics and search dashboard for Elasticsearch. Kibana strives to be easy to get started with, while also being flexible and powerful.
[Overview of Kibana](https://www.elastic.co/products/kibana)
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
### Docker Compose
### <a id="docker-compose"></a> Docker Compose
```console
docker run --name kibana bitnami/kibana: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?
@@ -32,15 +30,15 @@ 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).
## 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 Kibana Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/kibana).
@@ -62,9 +60,9 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .
```
## How to use this image
## <a id="how-to-use-this-image"></a> How to use this image
### Run the application manually
### <a id="run-the-application-manually"></a> Run the application manually
If you want to run the application manually instead of using the chart, these are the basic steps you need to run:
@@ -90,7 +88,7 @@ If you want to run the application manually instead of using the chart, these ar
Then you can access your application at `http://your-ip:5601/`
## Persisting your application
## <a id="persisting-your-application"></a> 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 application will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
@@ -104,15 +102,15 @@ To avoid inadvertent removal of these volumes you can [mount host directories as
docker run -v /path/to/kibana-persistence:/bitnami/kibana bitnami/kibana:latest
```
> NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
> **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 Kibana 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
### <a id="using-the-command-line"></a> Using the Command Line
#### Step 1: Create a network
@@ -140,12 +138,16 @@ docker run -d --name myapp \
> **IMPORTANT**:
>
> 1. Please update the **YOUR_APPLICATION_IMAGE_** placeholder in the above snippet with your application image
> 1. Please update the **YOUR_APPLICATION_IMAGE** placeholder in the above snippet with your application image
> 2. In your application container, use the hostname `kibana-server` to connect to the Kibana server
## Configuration
## <a id="configuration"></a> Configuration
### Environment variables
The following section describes the supported environment variables
### <a id="environment-variables"></a> Environment variables
The following tables list the main variables you can set.
#### Customizable environment variables
@@ -215,13 +217,13 @@ When you start the kibana image, you can adjust the configuration of the instanc
docker run -d -e KIBANA_ELASTICSEARCH_URL=elasticsearch --name kibana bitnami/kibana:latest
```
### Initializing a new instance
### <a id="initializing-a-new-instance"></a> Initializing a new instance
When the container is executed for the first time, it will execute the files with extension `.sh`, located at `/docker-entrypoint-initdb.d`.
In order to have your custom files inside the docker image you can mount them as a volume.
### Configuration file
### <a id="configuration-file"></a> Configuration file
The image looks for configurations in `/bitnami/kibana/conf/`. As mentioned in [Persisting your application](#persisting-your-application) you can mount a volume at `/bitnami` and copy/edit the configurations in the `/path/to/kibana-persistence/kibana/conf/`. The default configurations will be populated to the `conf/` directory if it's empty.
@@ -251,13 +253,13 @@ docker restart kibana
Refer to the [configuration](https://www.elastic.co/guide/en/kibana/current/settings.html) manual for the complete list of configuration options.
### FIPS configuration in Bitnami Secure Images
### <a id="fips-configuration"></a> FIPS configuration in Bitnami Secure Images
The Bitnami Kibana 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 Kibana Docker image sends the container logs to the `stdout`. To view the logs:
@@ -267,53 +269,9 @@ docker logs kibana
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.
## Maintenance
## <a id="notable-changes"></a> Notable Changes
### Upgrade this image
Bitnami provides up-to-date versions of Kibana, 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/kibana:latest
```
#### Step 2: Stop and backup the currently running container
Stop the currently running container using the command
```console
docker stop kibana
```
Next, take a snapshot of the persistent volume `/path/to/kibana-persistence` using:
```console
rsync -a /path/to/kibana-persistence /path/to/kibana-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)
```
Additionally, [snapshot the Elasticsearch data](https://github.com/bitnami/containers/blob/main/bitnami/elasticsearch#step-2-stop-and-backup-the-currently-running-container)
You can use these snapshots to restore the application state should the upgrade fail.
#### Step 3: Remove the currently running container
```console
docker rm -v kibana
```
#### Step 4: Run the new image
Re-create your container from the new image, restoring your backup if necessary.
```console
docker run --name kibana bitnami/kibana:latest
```
## Notable Changes
### Starting January 16, 2024
### <a id="starting-january-16-2024"></a> Starting January 16, 2024
- The `docker-compose.yaml` file has been removed, as it was solely intended for internal testing purposes.
@@ -333,7 +291,7 @@ docker run --name kibana bitnami/kibana:latest
- `ELASTICSEARCH_URL` parameter has been renamed to `KIBANA_ELASTICSEARCH_URL`.
- `ELASTICSEARCH_PORT` parameter has been renamed to `KIBANA_ELASTICSEARCH_PORT`.
## License
## <a id="license"></a> License
Copyright &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.