# Problem with the ElasticSearch docker image

**URL:** <https://discuss.elastic.co/t/problem-with-the-elasticsearch-docker-image/74676>\
**Category:** Elasticsearch\
**Created:** [February 10, 2017, 3:02pm UTC](https://discuss.elastic.co/t/problem-with-the-elasticsearch-docker-image/74676 "2017-02-10T15:02:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![brunoban](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brunoban/32/15428_2.png) [@brunoban](https://discuss.elastic.co/u/brunoban)\
**Post date:** [February 10, 2017, 3:02pm UTC](https://discuss.elastic.co/t/problem-with-the-elasticsearch-docker-image/74676/1 "2017-02-10T15:02:13Z")

</div>

I am running the Elastic Search Image from the docker repository, on a MacOS Sierra, following this guide [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html)

It advises me to use the following command to start it up

docker run -p 9200:9200 -e "http.host=0.0.0.0" -e "transport.host=127.0.0.1" --network=host [docker.elastic.co/elasticsearch/elasticsearch:5.2.0](http://docker.elastic.co/elasticsearch/elasticsearch:5.2.0)

However as soon as it's up, it gets killed.

I tried going starting it inside the container to see if there were any clues by using the following command:  
docker run -it -p 9200:9200 -e "http.host=0.0.0.0" -e "transport.host=127.0.0.1" --network=host [docker.elastic.co/elasticsearch/elasticsearch:5.2.0](http://docker.elastic.co/elasticsearch/elasticsearch:5.2.0) bash

But the only message that pops up is the "Killed" message.

Am I doing something terribly wrong?

Thanks

---

<div class="post-metadata">

**Author:** ![jwalsh](https://avatars.discourse-cdn.com/v4/letter/j/dc4da7/32.png) [@jwalsh](https://discuss.elastic.co/u/jwalsh)\
**Post date:** [February 27, 2017, 3:59am UTC](https://discuss.elastic.co/t/problem-with-the-elasticsearch-docker-image/74676/2 "2017-02-27T03:59:08Z")

</div>

same problem here. running 5.2.1

---

<div class="post-metadata">

**Author:** ![mentat](https://avatars.discourse-cdn.com/v4/letter/m/74df32/32.png) [@mentat](https://discuss.elastic.co/u/mentat)\
**Post date:** [February 28, 2017, 4:15pm UTC](https://discuss.elastic.co/t/problem-with-the-elasticsearch-docker-image/74676/3 "2017-02-28T16:15:44Z")

</div>

I'm running maxOS Sierra as well and it seems to be working for me:

`
docker run -p 9200:9200 -e "http.host=0.0.0.0" -e "transport.host=127.0.0.1" --network=host docker.elastic.co/elasticsearch/elasticsearch:5.2.2
[2017-02-28T16:11:48,344][INFO][o.e.n.Node] [] initializing ...
[2017-02-28T16:11:48,546][INFO][o.e.e.NodeEnvironment] [gRtxpin] using [1] data paths, mounts [[/ (overlay)]], net usable_space [52.6gb], net total_space [62.7gb], spins? [possibly], types [overlay]
[2017-02-28T16:11:48,546][INFO][o.e.e.NodeEnvironment] [gRtxpin] heap size [1.9gb], compressed ordinary object pointers [true]
[2017-02-28T16:11:48,548][INFO][o.e.n.Node] node name [gRtxpin] derived from node ID [gRtxpinyQpSs9LoOy8LXuQ]; set [node.name] to override
[2017-02-28T16:11:48,552][INFO][o.e.n.Node] version[5.2.2], pid[1], build[f9d9b74/2017-02-24T17:26:45.835Z], OS[Linux/4.9.4-moby/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/1.8.0_92-internal/25.92-b14]
[2017-02-28T16:11:50,252][INFO][o.e.p.PluginsService] [gRtxpin] loaded module [aggs-matrix-stats]
[2017-02-28T16:11:50,252][INFO][o.e.p.PluginsService] [gRtxpin] loaded module [ingest-common]
[2017-02-28T16:11:50,253][INFO][o.e.p.PluginsService] [gRtxpin] loaded module [lang-expression]
[2017-02-28T16:11:50,253][INFO][o.e.p.PluginsService] [gRtxpin] loaded module [lang-groovy]
[2017-02-28T16:11:50,253][INFO][o.e.p.PluginsService] [gRtxpin] loaded module [lang-mustache]
[2017-02-28T16:11:50,253][INFO][o.e.p.PluginsService] [gRtxpin] loaded module [lang-painless]
[2017-02-28T16:11:50,253][INFO][o.e.p.PluginsService] [gRtxpin] loaded module [percolator]
[2017-02-28T16:11:50,253][INFO][o.e.p.PluginsService] [gRtxpin] loaded module [reindex]
[2017-02-28T16:11:50,253][INFO][o.e.p.PluginsService] [gRtxpin] loaded module [transport-netty3]
[2017-02-28T16:11:50,253][INFO][o.e.p.PluginsService] [gRtxpin] loaded module [transport-netty4]
[2017-02-28T16:11:50,254][INFO][o.e.p.PluginsService] [gRtxpin] loaded plugin [x-pack]
[2017-02-28T16:11:50,711][WARN][o.e.d.s.g.GroovyScriptEngineService] [groovy] scripts are deprecated, use [painless] scripts instead
[2017-02-28T16:11:54,204][INFO][o.e.n.Node] initialized
[2017-02-28T16:11:54,204][INFO][o.e.n.Node] [gRtxpin] starting ...
[2017-02-28T16:11:54,728][INFO][o.e.t.TransportService] [gRtxpin] publish_address {127.0.0.1:9300}, bound_addresses {127.0.0.1:9300}
[2017-02-28T16:11:57,879][INFO][o.e.c.s.ClusterService] [gRtxpin] new_master {gRtxpin}{gRtxpinyQpSs9LoOy8LXuQ}{TAw-6K_1SN-QYc0YHjvd4Q}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-elected-as-master ([0] nodes joined)
[2017-02-28T16:11:57,905][INFO][o.e.h.HttpServer] [gRtxpin] publish_address {192.168.65.2:9200}, bound_addresses {[::]:9200}
[2017-02-28T16:11:57,906][INFO][o.e.n.Node] [gRtxpin] started
[2017-02-28T16:11:58,034][INFO][o.e.g.GatewayService] [gRtxpin] recovered [0] indices into cluster_state
[2017-02-28T16:11:58,655][INFO][o.e.l.LicenseService] [gRtxpin] license [c9ad500e-2bcc-4a41-9444-0f7b8a146c69] mode [trial] - valid
[2017-02-28T16:12:04,494][INFO][o.e.c.m.MetaDataCreateIndexService] [gRtxpin] [.monitoring-data-2] creating index, cause [auto(bulk api)], templates [.monitoring-data-2], shards [1]/[1], mappings [node, logstash, _default_, kibana, cluster_info]
[2017-02-28T16:12:04,671][INFO][o.e.c.m.MetaDataCreateIndexService] [gRtxpin] [.monitoring-es-2-2017.02.28] creating index, cause [auto(bulk api)], templates [.monitoring-es-2], shards [1]/[1], mappings [_default_, shards, node, index_stats, index_recovery, cluster_state, cluster_stats, node_stats, indices_stats]
[2017-02-28T16:12:05,073][INFO][o.e.c.m.MetaDataMappingService] [gRtxpin] [.monitoring-es-2-2017.02.28/nTlM43G9Qee56NhTo9RLVw] update_mapping [cluster_stats]
[2017-02-28T16:12:05,171][INFO][o.e.c.m.MetaDataMappingService] [gRtxpin] [.monitoring-es-2-2017.02.28/nTlM43G9Qee56NhTo9RLVw] update_mapping [node_stats]
[2017-02-28T16:12:15,481][INFO][o.e.c.m.MetaDataMappingService] [gRtxpin] [.monitoring-es-2-2017.02.28/nTlM43G9Qee56NhTo9RLVw] update_mapping [cluster_stats]
[2017-02-28T16:12:15,589][INFO][o.e.c.m.MetaDataMappingService] [gRtxpin] [.monitoring-es-2-2017.02.28/nTlM43G9Qee56NhTo9RLVw] update_mapping [indices_stats]
[2017-02-28T16:12:15,653][INFO][o.e.c.m.MetaDataMappingService] [gRtxpin] [.monitoring-es-2-2017.02.28/nTlM43G9Qee56NhTo9RLVw] update_mapping [index_stats]
`

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 28, 2017, 4:15pm UTC](https://discuss.elastic.co/t/problem-with-the-elasticsearch-docker-image/74676/4 "2017-03-28T16:15:47Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
