# Running elasticsearch 5.0.0 on a raspberry PI 3 **URL:** \ **Category:** Elasticsearch\ **Created:** [October 27, 2016, 9:14pm UTC](https://discuss.elastic.co/t/running-elasticsearch-5-0-0-on-a-raspberry-pi-3/64208 "2016-10-27T21:14:29Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![glagidse](https://avatars.discourse-cdn.com/v4/letter/g/b4bc9f/32.png) [@glagidse](https://discuss.elastic.co/u/glagidse)\ **Post date:** [October 27, 2016, 9:14pm UTC](https://discuss.elastic.co/t/running-elasticsearch-5-0-0-on-a-raspberry-pi-3/64208/1 "2016-10-27T21:14:29Z")
How can I run elasticsearch on a Raspberry Pi 3 over a network? If I try to run it on a localhost it works, but if I try to run it over a network I get the following error: [2016-10-27T23:09:39,941][INFO][o.e.t.TransportService] [node-1] publish\_address {192.168.0.151:9300}, bound\_addresses {192.168.0.151:9300} [2016-10-27T23:09:39,964][INFO][o.e.b.BootstrapCheck] [node-1] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks ERROR: bootstrap checks failed max virtual memory areas vm.max\_map\_count [65530] likely too low, increase to at least [262144] [2016-10-27T23:09:40,000][INFO][o.e.n.Node] [node-1] stopping ... [2016-10-27T23:09:40,082][INFO][o.e.n.Node] [node-1] stopped [2016-10-27T23:09:40,084][INFO][o.e.n.Node] [node-1] closing ... [2016-10-27T23:09:40,177][INFO][o.e.n.Node] [node-1] closed I understand that by reading the documentation that by setting network.hosts to a non local address sets elasticsearch up in production mode and adds a bunch of extra checks, but I don't want any of that. How can I run elasticsearch over a network without production mode? Raspberry pi doesn't have enough memory to run in production mode. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 27, 2016, 9:26pm UTC](https://discuss.elastic.co/t/running-elasticsearch-5-0-0-on-a-raspberry-pi-3/64208/2 "2016-10-27T21:26:09Z")
You can't. If host is set It means you need to fix all production potential issues. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 27, 2016, 11:06pm UTC](https://discuss.elastic.co/t/running-elasticsearch-5-0-0-on-a-raspberry-pi-3/64208/3 "2016-10-27T23:06:38Z")
> [@glagidse](#): > > Raspberry pi doesn't have enough memory to run in production mode What do you mean? Just set the heap lower. ---
**Author:** ![glagidse](https://avatars.discourse-cdn.com/v4/letter/g/b4bc9f/32.png) [@glagidse](https://discuss.elastic.co/u/glagidse)\ **Post date:** [October 27, 2016, 11:39pm UTC](https://discuss.elastic.co/t/running-elasticsearch-5-0-0-on-a-raspberry-pi-3/64208/4 "2016-10-27T23:39:21Z")
Doesn't work I've set -Xms512m -Xmx512m but that apparently isn't enough apparently, Raspberry pi 3 only has 1 gb ram. I figure I can get around it by creating a virtual network card and bridging it to my loopback address, because it works if I run it locally. But I've just gone back to an earlier version where it does work so it's all good. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 27, 2016, 11:39pm UTC](https://discuss.elastic.co/t/running-elasticsearch-5-0-0-on-a-raspberry-pi-3/64208/5 "2016-10-27T23:39:47Z")
> [@glagidse](#): > > but that apparently isn't enough apparently Apparently, why? ---
**Author:** ![glagidse](https://avatars.discourse-cdn.com/v4/letter/g/b4bc9f/32.png) [@glagidse](https://discuss.elastic.co/u/glagidse)\ **Post date:** [October 27, 2016, 11:44pm UTC](https://discuss.elastic.co/t/running-elasticsearch-5-0-0-on-a-raspberry-pi-3/64208/7 "2016-10-27T23:44:23Z")
Because the log says so: max virtual memory areas vm.max\_map\_count [65530] likely too low, increase to at least [262144] ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 27, 2016, 11:47pm UTC](https://discuss.elastic.co/t/running-elasticsearch-5-0-0-on-a-raspberry-pi-3/64208/8 "2016-10-27T23:47:00Z")
That's not heap, see [https://www.elastic.co/guide/en/elasticsearch/reference/5.0/\_maximum\_map\_count\_check.html](https://www.elastic.co/guide/en/elasticsearch/reference/5.0/_maximum_map_count_check.html) ---
**Author:** ![cmk1523](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cmk1523/32/6474_2.png) [@cmk1523](https://discuss.elastic.co/u/cmk1523)\ **Post date:** [March 16, 2017, 3:41am UTC](https://discuss.elastic.co/t/running-elasticsearch-5-0-0-on-a-raspberry-pi-3/64208/9 "2017-03-16T03:41:50Z")
Disabling the bootstrap check in the elasticsearch yml file should fix your problem ---
**Author:** ![Luca\_Belluccini](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/luca_belluccini/32/33239_2.png) [@Luca\_Belluccini](https://discuss.elastic.co/u/Luca_Belluccini)\ **Post date:** [April 13, 2017, 3:06pm UTC](https://discuss.elastic.co/t/running-elasticsearch-5-0-0-on-a-raspberry-pi-3/64208/10 "2017-04-13T15:06:42Z")
> [@glagidse](#): > > vm.max\_map\_count You can increase it in sysctl vm.max\_map\_count ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:01pm UTC](https://discuss.elastic.co/t/running-elasticsearch-5-0-0-on-a-raspberry-pi-3/64208/11 "2017-07-05T22:01:13Z")