pid failure preventing startup with ports forwarded about elasticsearch HOT 4 CLOSED

I am facing the same issue

from elasticsearch.

Mapped ports need to be sent to docker, not to the process running inside docker, so they need to come before the image name.

$ docker run -p 9200:9200 -p 9300:9300 --name es elasticsearch -Des.node.name="TestNode"

from elasticsearch.

Wow....I can't believe that was the problem. I've never seen ordering of arguments change the execution of the process, but.....learn a new thing every day.

Thanks!

from elasticsearch.

No problem! 😄 Order matters on commands more often than you think 😉, like git (git add -p vs git -p add). Everything after the image that you are running gets sent as arguments to the entrypoint or executed directly if there is no entrypoint. CenturyLink has a pretty good explanation of CMD and ENTRYPOINT. If the first argument looks like a flag, the entrypoint for elasticsearch sets permissions for /usr/share/elasticsearch/data and then passes all its arguments along to the elasticsearch executable, otherwise it just runs it, so that docker run -it elasticsearch bash just works.

from elasticsearch.