Public | Automated Build

Last pushed: 2 years ago
Short Description
Kibana 4 Dashboard, Stable release, Environment variable support, without elasticsearch server
Full Description

Dockerfile for Kibana v4

This Dockerfile contains the Kibana Dashboard. The default Kibana port 5601 is exposed.

To run this container you'll need a separate elasticsearch server.
Kibana automatically proxies all requests from the dashboard to the elasticsearch server. So the ES server doesn't need to be accessible from the internet.

Tags

Available Kibana Versions:

4.0.0-BETA2
4.0.0-BETA3
4.0.0-RC1
4.0.0
4.0.1
4.0.2
4.1.0
4.1.1
4.1.4, latest

Run

To connect to an elasticsearch server on the docker host, run this:

docker run -e ELASTICSEARCH=http://172.17.42.1:9200 -P marcbachmann/kibana4

Upgrade

from 4.0.0-RC1 to 4.0.0

There was a bug in the automatic config migration of Kibana 4.0.0-RC1.
If you're migrating from v4.0.0-RC1 to v4.0.0, you have to execute the following command.

BODY=`curl -XGET 'localhost:9200/.kibana/config/4.0.0-rc1/_source'`;
curl -XPUT "localhost:9200/.kibana/config/4.0.0" -d "$BODY" && curl -XDELETE "localhost:9200/.kibana/config/4.0.0-rc1"

Options

Most configuration variables can be set using environment variables.

ENV VAR         - default value
---------------------------------------
ELASTICSEARCH   = http://172.17.42.1:9200
KIBANA_INDEX    = .kibana
DEFAULT_APP_ID  = discover
REQUEST_TIMEOUT = 60
SHARD_TIMEOUT   = 30000
VERIFY_SSL      = true

Linking an Elasticsearch Container

When you're running Elasticsearch in a separate docker container, you can automatically link to it by naming the linked container elasticsearch. By doing so the ELASTICSEARCH variable gets automatically set. To link it correctly, it needs to expose the port 9200.

e.g.

docker run -d --name myElasticSearch elasticsearch
docker run -d --link myElasticSearch:elasticsearch -P marcbachmann/kibana4
Docker Pull Command
Owner
marcbachmann
Source Repository

Comments (3)
marcbachmann
2 years ago

I'm sorry that I didn't reply to the comments. I haven't received any notification.

@epelc I've added a port mapping example and highlighted the port in the first paragraph ;)

@tristan0x you're welcome

epelc
2 years ago

Great image but you should document that it runs on port 5601. I could see just using -P if it was port 80 but if your new to kibana 5601 is not apparent.

tristan0x
2 years ago

Very simple to use, and yet configurable. Perfect! Thank you!