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.el7 systemctl start dockerVerify Docker is running and pull the Elasticsearch image:
docker ps -a docker search elasticsearch docker pull elasticsearch:7.6.1 docker imagesRun Elasticsearch as a single‑node container:
docker run -d --name es2 -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" 41072cdeebc5 docker logs bae2d63e5f47Prepare a configuration file for Kibana and launch it:
mkdir -p /data/elk vim /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: true docker run -d --name=kibana --restart=always -p 5601:5601 -v /data/elk/kibana.yml:/usr/share/kibana/config/kibana.yml kibana:7.6.1 docker logs -f kibanaDownload and set up Cerebro for Elasticsearch cluster monitoring:
unzip cerebro-0.8.3.zip ln -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:// :5601 and Cerebro at http:// :9000 to monitor the Elasticsearch cluster.
Practical DevOps Architecture
Hands‑on DevOps operations using Docker, K8s, Jenkins, and Ansible—empowering ops professionals to grow together through sharing, discussion, knowledge consolidation, and continuous improvement.
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.