So I'm moving away from the xpack idea. It's enabled (all default settings) but I still have the network looking issue.
sudo netstat -nltp doesn't work for me, I tried it inside docker exec -it kibana bash
bash-4.2$ netstat
bash: netstat: command not found
Regardless, when I am inside the container I can successfully curl localhost:5601/app/kibana
It's outside the container that isn't working. I don't know where the problem lies (obviously), is it in the kibana image? Is it Docker? Is it my networking configuration of the box. I mean the same exact box works for elasticsearch. Different port though, but -p 9200:5601 for example didn't work either.
It does behave differently based on how I start up the container. if I do -p 5601:5601 neither of these curls work:
curl localhost:5601
curl 127.0.0.1:5601
but if I do --network=host both curls work.
Again, same box does one thing with es another with kibana. Docker is the same in both cases, this leads me to look at the image. I know for elasticsearch, I had to configure the bind and publish hosts. Can you do this for Kibana? It didn't complain but it didn't help.
network.bind_host: 0.0.0.0
network.publish_host: 123.45.67.88
My gut tells me it's something with the image and the way it is configured, but I can't prove that. Again, docker and the box/os are the same in es / kibana