# Elasticsearch on Raspberry Pi 3+

**URL:** <https://discuss.elastic.co/t/elasticsearch-on-raspberry-pi-3/179764>\
**Category:** Elasticsearch\
**Created:** [May 6, 2019, 12:09pm UTC](https://discuss.elastic.co/t/elasticsearch-on-raspberry-pi-3/179764 "2019-05-06T12:09:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![vatolin](https://avatars.discourse-cdn.com/v4/letter/v/ce7236/32.png) [@vatolin](https://discuss.elastic.co/u/vatolin)\
**Post date:** [May 6, 2019, 12:09pm UTC](https://discuss.elastic.co/t/elasticsearch-on-raspberry-pi-3/179764/1 "2019-05-06T12:09:22Z")

</div>

Hello.

I am an absolute beginner. I've purchased a Raspberry Pi 3+ and set up my own NextCloud. That works.

Now, I want to enable a full text search in my Nextcloud. Therefore, I want to install Elasticsearch on my Raspberry Pi. I've tried it as described [here](https://logz.io/blog/elk-stack-raspberry-pi/). But it ends in an error message:

`
pi@raspberrypi:/usr/share $ sudo mkdir /usr/share/elasticsearch
pi@raspberrypi:/usr/share $ cd /usr/share/elasticsearch
pi@raspberrypi:/usr/share/elasticsearch $ man wget
pi@raspberrypi:/usr/share/elasticsearch $ wget https://packages.elastic.co/GPG-KEY-elasticsearch
--2019-05-06 12:44:52-- https://packages.elastic.co/GPG-KEY-elasticsearch
Resolving packages.elastic.co (packages.elastic.co)... 151.101.114.217, 2a04:4e42:1b::729
Connecting to packages.elastic.co (packages.elastic.co)|151.101.114.217|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1768 (1.7K) [binary/octet-stream]
GPG-KEY-elasticsearch: Permission denied
Cannot write to ‘GPG-KEY-elasticsearch’ (Permission denied).
pi@raspberrypi:/usr/share/elasticsearch $ sudo apt-get install elasticsearch
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
elasticsearch
0 upgraded, 1 newly installed, 0 to remove and 13 not upgraded.
Need to get 0 B/19.1 kB of archives.
After this operation, 75.8 kB of additional disk space will be used.
dpkg: unrecoverable fatal error, aborting:
unknown user 'elasticsearch' in statoverride file
E: Sub-process /usr/bin/dpkg returned an error code (2)
`

What am I doing wrong?

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [May 6, 2019, 2:37pm UTC](https://discuss.elastic.co/t/elasticsearch-on-raspberry-pi-3/179764/2 "2019-05-06T14:37:39Z")

</div>

I would suggest that you install Elasticsearch on a different device, to use in conjunction with Nextcloud. An RPi3 is woefully underpowered to do this kind of thing. Just because a thing can be installed does not mean it will be useable after installation. The amount of RAM and the speed of disk access required for an Elasticsearch installation preclude an RPi3 from being used as pretty much anything else, if you also have Elasticsearch installed on it.

By the way, the article you reference is from 2017. A bit outdated, as there have been 2 major releases of Elasticsearch since then.

---

<div class="post-metadata">

**Author:** ![vatolin](https://avatars.discourse-cdn.com/v4/letter/v/ce7236/32.png) [@vatolin](https://discuss.elastic.co/u/vatolin)\
**Post date:** [May 6, 2019, 2:59pm UTC](https://discuss.elastic.co/t/elasticsearch-on-raspberry-pi-3/179764/3 "2019-05-06T14:59:05Z")

</div>

My approach is to have an Nextcloud in order to enable sharing of relevant PDF files of documents with family members and friends. All PDF files have been processed by ABBYY Finereader and are full text searchable. If it basically works, I probably will invest more money for hardware and acquire a more powerful computer than the RasPi.

But at the moment, I want to try and to learn whether it is at all worth to deploy such an own cloud. In this conjunction I at first want to install and enable Elasticsearch just experimentally.

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [May 6, 2019, 3:13pm UTC](https://discuss.elastic.co/t/elasticsearch-on-raspberry-pi-3/179764/4 "2019-05-06T15:13:11Z")

</div>

I recommend installing Elasticsearch manually, probably in the 6.7 release series. As far as running it as a proof-of-concept, it's quite possible that the system will be too taxed to effectively demonstrate proof-of-concept.

---

<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:** [June 3, 2019, 3:25pm UTC](https://discuss.elastic.co/t/elasticsearch-on-raspberry-pi-3/179764/5 "2019-06-03T15:25:18Z")

</div>

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