# Another Kibana instance appears to be migrating the index - Docker environment

**URL:** <https://discuss.elastic.co/t/another-kibana-instance-appears-to-be-migrating-the-index-docker-environment/248487>\
**Category:** Kibana\
**Tags:** docker\
**Created:** [September 14, 2020, 8:29am UTC](https://discuss.elastic.co/t/another-kibana-instance-appears-to-be-migrating-the-index-docker-environment/248487 "2020-09-14T08:29:30Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Stimmot](https://avatars.discourse-cdn.com/v4/letter/s/46a35a/32.png) [@Stimmot](https://discuss.elastic.co/u/Stimmot)\
**Post date:** [September 14, 2020, 8:59am UTC](https://discuss.elastic.co/t/another-kibana-instance-appears-to-be-migrating-the-index-docker-environment/248487/2 "2020-09-14T08:59:08Z")

</div>

Quick Update: the problem had to do with the indices not permitting writing/setting them to read-only due to storage problems. See my answer here: [Elasticsearch Docker: flood stage disk watermark [95%] exceeded](https://discuss.elastic.co/t/elasticsearch-docker-flood-stage-disk-watermark-95-exceeded/248479/2)

After manually updating the settings, the indices kibana\_1 and kibana\_task\_manager\_1 can be deleted by using

```auto
curl -XDELETE 'http://localhost:9200/.kibana_1' --header "content-type: application/JSON" -u elastic -p

```

After that it will work.

---

_[View the full topic](https://discuss.elastic.co/t/another-kibana-instance-appears-to-be-migrating-the-index-docker-environment/248487)._