# How to properly upgrade ElasticSearch running as docker containers

**URL:** <https://discuss.elastic.co/t/how-to-properly-upgrade-elasticsearch-running-as-docker-containers/221711>\
**Category:** Elasticsearch\
**Created:** [March 2, 2020, 3:17pm UTC](https://discuss.elastic.co/t/how-to-properly-upgrade-elasticsearch-running-as-docker-containers/221711 "2020-03-02T15:17:56Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [March 2, 2020, 4:07pm UTC](https://discuss.elastic.co/t/how-to-properly-upgrade-elasticsearch-running-as-docker-containers/221711/2 "2020-03-02T16:07:04Z")

</div>

The Elasticsearch-centric docs for upgrades are [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html#setup-upgrade). You can indeed start a 7.6.0 node on top of data from a 7.5.0 node and let Elasticsearch handle the upgrade automatically, so there's no need to regenerate anything or worry about schema changes.

Unfortunately I don't know how to translate this into the changes you need for your `docker-compose.yml`, but note that the section on [preparing to upgrade](https://www.elastic.co/guide/en/elasticsearch/reference/current/rolling-upgrades.html#_preparing_to_upgrade) says:

> 1. Test the upgrade in an isolated environment before upgrading your production cluster.

Please do this!

---

_[View the full topic](https://discuss.elastic.co/t/how-to-properly-upgrade-elasticsearch-running-as-docker-containers/221711)._