kibana 4.4.1 in docker times out communicating via an overlay network with elasticsearch 2.2.0 in docker

[dfwcnj]

this is related to issue #6372 that I believe was closed in haste.

the elasticsearch container is machine local, the machine is quiet. the latency for this simple curl call is mostly over 2000 ms. the hard coded value in health_check.js works fine outside docker as well as in docker when they are communicating over a bridge.
the machinery introduced with an overlay network introduces a lot of copies between the processes - 2 veth pairs, 2 bridged and a vxlan. Hard coded values are not commonly justified in my opinion. As it is, I use a sed script to change the value so that it sort of works. Once I get to the UI, I can set up some auto refreshed visualizations. I am reminded that there is most likely some other possibly hard coded value lurking when I reload the page and sometimes have to traverse a red and green status page before returning to my visualization.

time curl -i http://elasticsearch01:9200/
HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Content-Length: 305

{
"name" : "EL5",
"cluster_name" : "ULDemo",
"version" : {
"number" : "2.2.0",
"build_hash" : "8ff36d139e16f8720f2947ef62c8167a888992fe",
"build_timestamp" : "2016-01-27T13:32:39Z",
"build_snapshot" : false,
"lucene_version" : "5.4.1"
},
"tagline" : "You Know, for Search"
}

real 0m2.522s
user 0m0.004s
sys 0m0.004s

[rashidkpc]

Again, already fixed: #6377