# Elasticsearch 8.3.2 docker org.elasticsearch.gateway.CorruptStateException

**URL:** <https://discuss.elastic.co/t/elasticsearch-8-3-2-docker-org-elasticsearch-gateway-corruptstateexception/310765>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [July 27, 2022, 3:03pm UTC](https://discuss.elastic.co/t/elasticsearch-8-3-2-docker-org-elasticsearch-gateway-corruptstateexception/310765 "2022-07-27T15:03:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zelfapp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zelfapp/32/108888_2.png) [@Zelfapp](https://discuss.elastic.co/u/Zelfapp)\
**Post date:** [July 27, 2022, 3:03pm UTC](https://discuss.elastic.co/t/elasticsearch-8-3-2-docker-org-elasticsearch-gateway-corruptstateexception/310765/1 "2022-07-27T15:03:45Z")

</div>

Installed ES 8.3.2 using docker on my local dev machine. Before this installation I had ES 6.3.2 running and I had deleted all my test indices in 6.3.2 before installing 8.3.2 so that I would avoid any v6 issues with 8 on my local dev. When I attempt `docker-compose up --build` I get this error:

```auto
es_usamm-db | org.elasticsearch.ElasticsearchException: failed to bind service
es_usamm-db | Likely root cause: org.elasticsearch.gateway.CorruptStateException: Format version is not supported. Upgrading to [8.3.2] is only supported from version [7.17.0].

```

How do I completely wipe out any elasticsearch docker data so that I can just install 8.3.2? I thought deleting all indices in 6.3.2 would have allowed a clean install of 8.3.2, but there must still be some 6.3.2 data persisting somewhere?

Here is my `docker-compose.yml`

```auto
services:
  elasticsearch:
    container_name: es_usamm-db
    image: docker.elastic.co/elasticsearch/elasticsearch:8.3.2
    environment:
      - node.name=es01
      - cluster.name=es-docker-cluster
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
      - xpack.security.enabled=false
      - discovery.type=single-node
    ulimits:
      memlock:
        soft: -1
        hard: -1
    volumes:
      - data01:/usr/share/elasticsearch/data
      - ./server/elastic/scripts:/server/elastic/scripts
    ports:
      - 9200:9200
    networks:
      - default
  kibana:
    container_name: kibana_usamm-db
    image: docker.elastic.co/kibana/kibana:8.3.2
    ports:
      - 5601:5601
    networks:
      - default

```

---

<div class="post-metadata">

**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:** [July 27, 2022, 11:17pm UTC](https://discuss.elastic.co/t/elasticsearch-8-3-2-docker-org-elasticsearch-gateway-corruptstateexception/310765/2 "2022-07-27T23:17:19Z")

</div>

> [@Zelfapp](#):
>
> How do I completely wipe out any elasticsearch docker data so that I can just install 8.3.2? I thought deleting all indices in 6.3.2 would have allowed a clean install of 8.3.2, but there must still be some 6.3.2 data persisting somewhere?

Can you elaborate more on what you did when you said you deleted the indices?

You should really be using a different `volumes:` value, if `data01` was what you used for 6.X. That way you don't need to worry about deleting anything, as it'll be a new data directory.

---

<div class="post-metadata">

**Author:** ![Zelfapp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zelfapp/32/108888_2.png) [@Zelfapp](https://discuss.elastic.co/u/Zelfapp)\
**Post date:** [July 27, 2022, 11:35pm UTC](https://discuss.elastic.co/t/elasticsearch-8-3-2-docker-org-elasticsearch-gateway-corruptstateexception/310765/3 "2022-07-27T23:35:06Z")

</div>

I did end up using a different volume i.e. `data02` to get past the error.

To answer your question, when v6 was running, in dev tools kibana, I ran `DELETE _all`. Everything was wiped out, which was confusing when I tried to run v8 on the `data01` volume. Anyway, changing the volume fixed it.

---

<div class="post-metadata">

**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:** [July 27, 2022, 11:39pm UTC](https://discuss.elastic.co/t/elasticsearch-8-3-2-docker-org-elasticsearch-gateway-corruptstateexception/310765/4 "2022-07-27T23:39:14Z")

</div>

That's what I figured you did.

But that doesn't remove things like cluster state, which is probably part of the reason you ran into this issue.

---

<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:** [August 24, 2022, 11:39pm UTC](https://discuss.elastic.co/t/elasticsearch-8-3-2-docker-org-elasticsearch-gateway-corruptstateexception/310765/5 "2022-08-24T23:39:54Z")

</div>

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