Deploying Elasticsearch, Kibana, and Cerebro with Docker on a Linux Node
This tutorial walks through installing Docker CE on CentOS, then pulling and running Elasticsearch and Kibana containers, configuring Kibana, and setting up the Cerebro monitoring tool, providing all necessary commands and configuration snippets for a complete ELK stack deployment.
This guide demonstrates how to install Docker CE on a CentOS 7 host and use it to deploy Elasticsearch 7.6.1, Kibana 7.6.1, and the Cerebro monitoring UI.
Install Docker CE:
yum -y install docker-ce-20.10.4-3.el7systemctl start dockerVerify Docker is running and pull the Elasticsearch image:
docker ps -adocker search elasticsearchdocker pull elasticsearch:7.6.1docker imagesRun Elasticsearch as a single‑node container:
docker run -d --name es2 -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" 41072cdeebc5docker logs bae2d63e5f47Prepare a configuration file for Kibana and launch it:
mkdir -p /data/elkvim /data/elk/kibana.yml# Example kibana.yml content
server.name: kibana
server.host: "0"
elasticsearch.hosts: [ "http://192.xx.xx.xx:9200" ]
xpack.monitoring.ui.container.elasticsearch.enabled: truedocker run -d --name=kibana --restart=always -p 5601:5601 -v /data/elk/kibana.yml:/usr/share/kibana/config/kibana.yml kibana:7.6.1docker logs -f kibanaDownload and set up Cerebro for Elasticsearch cluster monitoring:
unzip cerebro-0.8.3.zipln -s cerebro-0.8.3 cerebro# Edit /root/cerebro/conf/application.conf
hosts = [
{
host = "http://192.xx.xx.xx:9200"
name = "en-es"
headers-whitelist = [ "x-proxy-user", "x-proxy-roles", "X-Forwarded-For" ]
}
]./cerebro -Dhttp.port=9000 -Dhttp.address=192.xx.xx.xx >/dev/null &After starting the services, access Kibana at http://<your‑host>:5601 and Cerebro at http://<your‑host>:9000 to monitor the Elasticsearch cluster.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
