# /usr/share/elasticsearch/data isn't in-line with the FHS (filesystem hierarchy standard)?

**URL:** <https://discuss.elastic.co/t/usr-share-elasticsearch-data-isnt-in-line-with-the-fhs-filesystem-hierarchy-standard/104090>\
**Category:** Elasticsearch\
**Created:** [October 16, 2017, 12:31pm UTC](https://discuss.elastic.co/t/usr-share-elasticsearch-data-isnt-in-line-with-the-fhs-filesystem-hierarchy-standard/104090 "2017-10-16T12:31:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![JPvRiel](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@JPvRiel](https://discuss.elastic.co/u/JPvRiel)\
**Post date:** [October 16, 2017, 12:31pm UTC](https://discuss.elastic.co/t/usr-share-elasticsearch-data-isnt-in-line-with-the-fhs-filesystem-hierarchy-standard/104090/1 "2017-10-16T12:31:29Z")

</div>

As per [Filesystem Hierarchy Standard](http://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.html#usrshareArchitectureindependentData)

> The /usr/share hierarchy is for all read-only architecture independent data files.

The example from elasticsearch at [Install Elasticsearch with Docker | Elasticsearch Guide [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html) does not adhere to the guidance in the FHS?

For example, in other cases:

- the default for elasticsearch (running on a host, not a container) was `/var/lib/elasticsearch`?
- the default for the official mqsql container is `/var/lib/mysql`?

So I'd argue a good and compliant example might be `-v /var/lib/elasticsearch/container/data:/var/lib/elasticsearch` instead of `/usr/share/elasticsearch/data`

---

<div class="post-metadata">

**Author:** ![JPvRiel](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@JPvRiel](https://discuss.elastic.co/u/JPvRiel)\
**Post date:** [October 16, 2017, 12:43pm UTC](https://discuss.elastic.co/t/usr-share-elasticsearch-data-isnt-in-line-with-the-fhs-filesystem-hierarchy-standard/104090/2 "2017-10-16T12:43:17Z")

</div>

While this is a smallish issue, note examples like:

> Specifically, when using Red Hat Enterprise Linux Atomic Host, the operating system content is mounted in read-only mode. There are only two writable directories for local system configuration: /etc/ and /var/.

> **[Chapter 1. Introduction to Atomic Host Red Hat Enterprise Linux...](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html/installation_and_configuration_guide/introduction_to_atomic_host)**
>
> Access Red Hat’s knowledge, guidance, and support through your subscription.

The other interesting piece is `docker-lvm-plugin`, but probably only applicable to RHEL / CentOS / Fedora.

---

<div class="post-metadata">

**Author:** ![rjernst](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rjernst/32/6363_2.png) [@rjernst](https://discuss.elastic.co/u/rjernst)\
**Post date:** [November 10, 2017, 6:46pm UTC](https://discuss.elastic.co/t/usr-share-elasticsearch-data-isnt-in-line-with-the-fhs-filesystem-hierarchy-standard/104090/3 "2017-11-10T18:46:50Z")

</div>

You could open an enhancement request in the [ES docker repo](https://github.com/elastic/elasticsearch-docker), as it is really an issue there (how ES is started).

---

<div class="post-metadata">

**Author:** ![JPvRiel](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@JPvRiel](https://discuss.elastic.co/u/JPvRiel)\
**Post date:** [November 17, 2017, 6:39pm UTC](https://discuss.elastic.co/t/usr-share-elasticsearch-data-isnt-in-line-with-the-fhs-filesystem-hierarchy-standard/104090/4 "2017-11-17T18:39:18Z")

</div>

Thanks, will do now

---

<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:** [December 15, 2017, 6:39pm UTC](https://discuss.elastic.co/t/usr-share-elasticsearch-data-isnt-in-line-with-the-fhs-filesystem-hierarchy-standard/104090/5 "2017-12-15T18:39:20Z")

</div>

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