balsamiq / docker-kibana Goto Github PK

How do I pass in elasticsearch username and password?

Hi,

When launching run the first time, the es address is set from $ES_PORT_9200_TCP_ADDR. But if we restart the container and es address change, the change won't be made in the yml file (as it replace "localhost" to ES_PORT_9200_TCP_ADDR, but "localhost" has already been replace the first time).

I'm new to docker, but should'nt we be using the hostname in that config file ? If we use "es" it will use the ip address available in the host file.

Thanks for this container! I've been using this along with the balsamiq/docker-elasticsearch container out of the Docker Hub Registry, and I've noticed that occasionally (maybe one out of four or five starts) nginx can't bind to port 80 at start, so nginx is running but nothing is listening on port 80. If I nsenter the container and restart nginx, all is well.

Here's how I'm starting the containers:

docker run -itd --name es1 --hostname es1 balsamiq/docker-elasticsearch
docker run -itd -e KIBANA_SECURE=false --link es1:es --name kib1 --hostname kib1 balsamiq/docker-kibana

I don't need to access it from outside the host, so I'm not exposing the ports.

Here's the nginx error.log:

2014/07/29 02:05:34 [emerg] 49#0: bind() to 0.0.0.0:80 failed (98: Address already in use)
2014/07/29 02:05:34 [emerg] 49#0: bind() to [::]:80 failed (98: Address already in use)
2014/07/29 02:05:34 [emerg] 49#0: bind() to 0.0.0.0:80 failed (98: Address already in use)
2014/07/29 02:05:34 [emerg] 49#0: bind() to [::]:80 failed (98: Address already in use)
2014/07/29 02:05:34 [emerg] 49#0: bind() to 0.0.0.0:80 failed (98: Address already in use)
2014/07/29 02:05:34 [emerg] 49#0: bind() to [::]:80 failed (98: Address already in use)
2014/07/29 02:05:34 [emerg] 49#0: bind() to 0.0.0.0:80 failed (98: Address already in use)
2014/07/29 02:05:34 [emerg] 49#0: bind() to [::]:80 failed (98: Address already in use)
2014/07/29 02:05:34 [emerg] 49#0: bind() to 0.0.0.0:80 failed (98: Address already in use)
2014/07/29 02:05:34 [emerg] 49#0: bind() to [::]:80 failed (98: Address already in use)
2014/07/29 02:05:34 [emerg] 49#0: still could not bind()

I'm suspecting that maybe something is off in the supervisord config, but I haven't been able to spot it. Have you noticed this behavior? I think I may fork this and just replace supervisord with runit to see if that makes a difference, because I haven't really seen anything like this with my runit+nginx containers.

When I run this container (on AWS), I'm getting the following error:

Uncaught ReferenceError: ZeroClipboard is not defined (http://.../index.js?_b=6004:89886)
Error: Uncaught ReferenceError: ZeroClipboard is not defined (http://.../index.js?_b=6004:89886)
at window.onerror (http://.../index.js?_b=6004:45829:24)

Anyone else getting this error?