Public | Automated Build

Last pushed: a month ago
Short Description
Elasticsearch-5.5.1 Kibana-5.5.1
Full Description

Elasticsearch and Kibana in one container

Simple and lightweight docker image for previewing Elasticsearch and Kibana.

Usage

docker run -d -p 9200:9200 -p 5601:5601 nshou/elasticsearch-kibana

Then you can connect to Elasticsearch by localhost:9200 and its Kibana front-end by localhost:5601.

Tags

Tag Elasticsearch Kibana
latest 5.5.1 5.5.1
kibana4 2.4.1 4.6.2
kibana3 1.7.4 3.1.3
Docker Pull Command
Owner
nshou
Source Repository

Comments (10)
nshou
24 days ago

Thank you sherzod, if you don't mind please copy and paste the contents of your jvm.options here.

sherzod
25 days ago

I too had a memory issue when using this image in a docker-compose. Ended up lowering the memory in jvm.options

version: '3.2'
services:
  ek5:
    image: nshou/elasticsearch-kibana:latest
    ports: ["9200:9200", "5601:5601"]
    volumes:
      - type: bind
        source: ${PWD}/elasticsearch/config/jvm.options
        target: /home/elasticsearch/elasticsearch/config/jvm.options
nshou
5 months ago

Hello akrymets, did you try limiting JAVA heap size? That can be controlled through an environment variable ES_JAVA_OPTS, adding -e ES_JAVA_OPTS="-Xms256m -Xmx256m" to docker run command for example. If your system still reproduces memory-related errors even after doing it, you might have to tweak elasticsearch.yml to make it fit for your physical memory setting. Please see https://www.elastic.co/guide/en/elasticsearch/guide/current/heap-sizing.html and https://www.elastic.co/guide/en/elasticsearch/guide/current/_limiting_memory_usage.html for more detail.

akrymets
5 months ago

I got "Out of Memory Error" in the hs_err_pid7.log right after running the container. Is there a way to configure it? Thanks

nshou
6 months ago

Hi hosar. Yes you can make Elasticsearch data persistent by bind-mounting -v /PATH/TO/DIR:/home/elasticsearch/elasticsearch/data, and you can also override existing config files by -v /PATH/TO/FILE:/home/elasticsearch/elasticsearch/config/elasticsearch.yml for Elasticsearch, or by -v /PATH/TO/FILE:/home/elasticsearch/kibana/config/kibana.yml for Kibana.

hosar
7 months ago

Hi nshou, does the container support a volume?

nshou
8 months ago

Hi meeximum,
I believe it was docker side problem, not this image's. Did you try restarting docker daemon or something like that? Please email me then I will help you until you eventually run the container.

meeximum
8 months ago

When I try to run the image, I get this error?

docker: Error response from daemon: driver failed programming external connectivity on endpoint condescending_jones (2a9ab9c42fb81a20a9d39ef38e4bbf544f925a0b46e4bd1dcf731cddece9db53): i ptables failed: iptables --wait -t filter -A DOCKER ! -i docker0 -o docker0 -p tcp -d 172.17.0.2 --dport 9200 -j ACCEPT: iptables: No chain/target/match by that name.

nshou
2 years ago

Hello harit,
Files are hosted at https://bitbucket.org/nshou/elasticsearch-kibana by mercurial so you can just fork it and send me a pull request. Or, it is also OK you simply create a copy and publish it as your another repository. Thanks.

harit
2 years ago

I wanted to add a Marvel plugin that I did by copying your Dockerfile, is there a way I clone your dockerfile and update with my change?