In order to unify the approaches followed for Bitnami containers and Bitnami Helm charts, we are moving the different bitnami/bitnami-docker-<container> repositories to a single monorepo bitnami/containers. Please follow bitnami/containers to keep you updated about the latest Bitnami images.

More information here: https://blog.bitnami.com/2022/07/new-source-of-truth-bitnami-containers.html

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

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.

$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-kibana/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d

• Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
• With Bitnami images the latest bug fixes and features are available as soon as possible.
• Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
• All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading Linux distribution.
• All Bitnami images available in Docker Hub are signed with Docker Content Trust (DCT). You can use DOCKER_CONTENT_TRUST=1 to verify the integrity of the images.
• Bitnami container images are released on a regular basis with the latest distribution packages available.

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.

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

• 8, 8-debian-11, 8.3.2, 8.3.2-debian-11-r7, latest (8/debian-11/Dockerfile)
• 7, 7-debian-11, 7.17.5, 7.17.5-debian-11-r11 (7/debian-11/Dockerfile)

Subscribe to project updates by watching the bitnami/kibana GitHub repo.

The recommended way to get the Bitnami Kibana Docker Image is to pull the prebuilt image from the Docker Hub Registry.

$ docker pull bitnami/kibana:latest

To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.

$ docker pull bitnami/kibana:[TAG]

If you wish, you can also build the image yourself.

$ docker build -t bitnami/kibana:latest 'https://github.com/bitnami/bitnami-docker-kibana.git#master:8/debian-11'

The main folder of this repository contains a functional docker-compose.yml file. Run the application using it as shown below:

$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-kibana/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d

If you want to run the application manually instead of using docker-compose, these are the basic steps you need to run:

1. Create a new network for the application and the database:

$ docker network create kibana_network

2. Run the Elasticsearch container:

$ docker run -d -p 9200:9200 --name elasticsearch --net=kibana_network bitnami/elasticsearch

3. Run the Kibana container:

$ docker run -d -p 5601:5601 --name kibana --net=kibana_network \
  -e KIBANA_ELASTICSEARCH_URL=elasticsearch \
  bitnami/kibana

Then you can access your application at http://your-ip:5601/

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.

For persistence you should mount a volume at the /bitnami path. Additionally you should mount a volume for persistence of the Elasticsearch data.

The above examples define docker volumes namely elasticsearch_data and kibana_data. The Kibana application state will persist as long as these volumes are not removed.

To avoid inadvertent removal of these volumes you can mount host directories as data volumes. Alternatively you can make use of volume plugins to host the volume data.

$ docker run -v /path/to/kibana-persistence:/bitnami/kibana bitnami/kibana:latest

or modifying the docker-compose.yml file present in this repository:

kibana:
  ...
  volumes:
    - /path/to/kibana-persistence:/bitnami/kibana
  ...

NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID 1001.

Using Docker container 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.

$ docker network create app-tier --driver bridge

Use the --network app-tier argument to the docker run command to attach the Kibana container to the app-tier network.

$ docker run -d --name kibana-server \
    --network app-tier \
    bitnami/kibana:latest

$ docker run -d --name myapp \
    --network app-tier \
    YOUR_APPLICATION_IMAGE

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 kibana-server to connect to the Kibana server

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 Kibana server from your own custom application image which is identified in the following snippet by the service name myapp.

version: '2'

networks:
  app-tier:
    driver: bridge

services:
  kibana:
    image: 'bitnami/kibana: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 kibana to connect to the Kibana server

Launch the containers using:

$ docker-compose up -d

When you start the kibana 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. The following environment values are provided to custom Kibana:

• KIBANA_ELASTICSEARCH_URL: Elasticsearch URL. Provide Client node url in the case of a cluster. Default: elasticsearch
• KIBANA_ELASTICSEARCH_PORT_NUMBER: Elasticsearch port. Default: 9200
• KIBANA_HOST: Kibana host. Default: 0.0.0.0
• KIBANA_PORT_NUMBER: Kibana port. Default: 5601
• KIBANA_WAIT_READY_MAX_RETRIES: Max retries to wait for Kibana to be ready. Default: 30
• KIBANA_INITSCRIPTS_START_SERVER: Whether to start the Kibana server before executing the init scripts. Default: yes
• KIBANA_FORCE_INITSCRIPTS: Whether to force the execution of the init scripts. Default: no

This requires a minor change to the docker-compose.yml file present in this repository:

kibana:
  ...
  environment:
    - KIBANA_ELASTICSEARCH_URL=elasticsearch
  ...

$ docker run -d -e KIBANA_ELASTICSEARCH_URL=elasticsearch --name kibana bitnami/kibana:latest

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.

The image looks for configurations in /bitnami/kibana/conf/. As mentioned in 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.

Run the Kibana image, mounting a directory from your host.

$ docker run --name kibana -v /path/to/kibana-persistence:/bitnami bitnami/kibana:latest

or modifying the docker-compose.yml file present in this repository:

kibana:
  ...
  volumes:
    - /path/to/kibana-persistence:/bitnami/kibana
  ...

Edit the configuration on your host using your favorite editor.

$ vi /path/to/kibana-persistence/kibana/conf/kibana.conf

After changing the configuration, restart your Kibana container for changes to take effect.

$ docker restart kibana

or using Docker Compose:

$ docker-compose restart kibana

Refer to the configuration manual for the complete list of configuration options.

The Bitnami Kibana Docker image sends the container logs to the stdout. To view the logs:

$ docker logs kibana

or using Docker Compose:

$ docker-compose logs kibana

You can configure the containers logging driver using the --log-driver option if you wish to consume the container logs differently. In the default configuration docker uses the json-file driver.

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.

$ docker pull bitnami/kibana:latest

or if you're using Docker Compose, update the value of the image property to bitnami/kibana:latest.

Stop the currently running container using the command

$ docker stop kibana

or using Docker Compose:

$ docker-compose stop kibana

Next, take a snapshot of the persistent volume /path/to/kibana-persistence using:

$ rsync -a /path/to/kibana-persistence /path/to/kibana-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)

Additionally, snapshot the Elasticsearch data

You can use these snapshots to restore the application state should the upgrade fail.

$ docker rm -v kibana

or using Docker Compose:

$ docker-compose rm -v kibana

Re-create your container from the new image, restoring your backup if necessary.

$ docker run --name kibana bitnami/kibana:latest

or using Docker Compose:

$ docker-compose up kibana

• The size of the container image has been decreased.
• The configuration logic is now based on Bash scripts in the rootfs/ folder.
• Kibana 7.12.0 version or later are licensed under the Elastic License that is not currently accepted as an Open Source license by the Open Source Initiative (OSI).
• Kibana 7.12.0 version or later are including x-pack plugin installed by default. Follow official documentation to use it.

• The Kibana container has been migrated to a non-root user approach. Previously the container ran as the root user and the Kibana daemon was started as the kibana user. From now on, both the container and the Kibana daemon run as user 1001. As a consequence, the data directory must be writable by that user. You can revert this behavior by changing USER 1001 to USER root in the Dockerfile.

• ELASTICSEARCH_URL parameter has been renamed to KIBANA_ELASTICSEARCH_URL.
• ELASTICSEARCH_PORT parameter has been renamed to KIBANA_ELASTICSEARCH_PORT.

We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.

If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:

• Host OS and version
• Docker version (docker version)
• Output of docker info
• Version of this container
• The command you used to run the container, and any relevant output you saw (masking any sensitive information)

Copyright © 2022 Bitnami

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.