Manticore has lost its index

Nobody has claimed this yet.

### Confirmation Checklist:

- [X] You have searched for an answer in [the manual](https://manual.manticoresearch.com/).
- [X] You have considered using [the forum](https://forum.manticoresearch.com/) for general discussions, which can be more suitable for non-urgent or broad queries.
- [X] You are aware of our community support channels on [Slack](https://slack.manticoresearch.com/), [Telegram EN](https://t.me/manticoresearch_en), and [Telegram RU](https://t.me/manticore_chat), where you can interact with other users and our developers.
- [X] You know about Manticore Team's [professional services](https://manticoresearch.com/services). Engaging with our experts through a support subscription can significantly accelerate resolution times and provide tailored solutions to your specific needs.

### Your question:

I am using manticore as a search backend for mailpiler.org. Today i experienced an issue where manticore has lost its indexes. At first i opened an issue against piler (https://github.com/jsuto/piler/issues/179) and as a result the developer suggested that i should mount manticore's data as a persistent volume/folder, which is what i already did: https://github.com/jsuto/piler/issues/179#issuecomment-2328243984

Fortunately, piler has a command which allows it to recreate its indexes. However, this seems to be more a manticore than a piler issue, so i am asking for help: Do i mount the right folder? I followed the README of the manticore docker container and persisted the whole /var/lib/manticore folder. I am using this manticore.conf: https://github.com/jsuto/piler/blob/master/docker/manticore.conf

I could need some hints towards the right way to persist manticore's data to not lose the index again. What am i doing wrong?

Start with the Manticore Docker README and the referenced piler docker/manticore.conf, focusing on persistence for /var/lib/manticore. Review the linked piler issue and its discussion for the existing setup and the index-recreation behavior. Done means identifying why the persisted index is lost and confirming a reliable data mount or configuration.

Written by the indexing model from the issue text.