在Docker中配置Kibana连接ElasticSearch的一些小坑

之前编译部署的时候只需要在config/kibana.yaml 中修改host ,把默认的 http://elasticsearch:9200 改为 http://127.0.0.1:9200 , 如果你的ElasticSearch带密码访问，只需在下面加多2行
elasticseacrh.user='elastic'
elasticsearch.password='xxxxxx'  # 你之前配置ES时设置的密码
 
BUT, 上面的配置在docker环境下无法正常启动使用kibana， 通过docker logs 容器ID， 查看的日志信息：
 

  log   [17:39:09.057] [warning][data][elasticsearch] No living connections

  log   [17:39:09.058] [warning][licensing][plugins] License information could not be obtained from Elasticsearch due to Error: No Living connections error

  log   [17:39:09.635] [warning][admin][elasticsearch] Unable to revive connection: http://127.0.0.1:9200/

  log   [17:39:09.636] [warning][admin][elasticsearch] No living connections

  log   [17:39:12.137] [warning][admin][elasticsearch] Unable to revive connection: http://127.0.0.1:9200/

  log   [17:39:12.138] [warning][admin][elasticsearch] No living connections

  log   [17:39:14.640] [warning][admin][elasticsearch] Unable to revive connection: http://127.0.0.1:9200/

  log   [17:39:14.640] [warning][admin][elasticsearch] No living connections

  log   [17:39:17.143] [warning][admin][elasticsearch] Unable to revive connection: http://127.0.0.1:9200/

  log   [17:39:17.143] [warning][admin][elasticsearch] No living connections

  log   [17:39:19.645] [warning][admin][elasticsearch] Unable to revive connection: http://127.0.0.1:9200/

使用curl访问127.0.0.1:920也是正常的，后来想到docker貌似没有配置桥接网络，两个docker可能无法互通，故把kibana.yaml里面的host改为主机的真实IP（内网172网段ip），然后问题就得到解决了。