Jan Stabenow

in my case the problem is a static configured `--default.network.publish_host=_non_loopback:ipv4_`. I have tested this with DC/OS on Docker and the executor always takes the IPv4 of the spartan interface. A...

@zsmith928 I also had trouble with this package on DCOS-Docker and have tried to find a solution. Would be nice if you can verify if it also runs on your...

update: https://github.com/mesos/elasticsearch/pull/569

hey @jbirch that sounds after a similar problem. On Google there are many articles about network problems with Elasticsearch / Java. That's why I added the `publish_host` as a parameter....

Hey @jbirch no problem :-) Please try `${ENV}` instead of `$ENV` ``` sh $ docker run -it --net=host elasticsearch:latest --default.network.publish_host=${LIBPROCESS_IP} $ docker run -it --net=host elasticsearch:latest --default.network.publish_host=${HOST} ``` This two...

Ah sorry ... this can't work because it's not created by Mesos = No ENV ;-) Please try my ES-Package again and replace ${LIBPROCESS_IP} with ${HOST}. But that was supposed...

Hey @philwinder No problem. I will close my PR.

Hey @noho501 Should the processes be displayed in the user interface?

Yes, no problem. But it takes some time. So I will answer you in the coming days.

> Hi @jstabenow Any updates? I am working on a CLI with which you can read out, edit or create all processes, for example. That should help you with your...