# Should I move ES to Docker?

**URL:** <https://discuss.elastic.co/t/should-i-move-es-to-docker/109110>\
**Category:** Elasticsearch\
**Created:** [November 25, 2017, 5:24pm UTC](https://discuss.elastic.co/t/should-i-move-es-to-docker/109110 "2017-11-25T17:24:30Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![prophoto](https://avatars.discourse-cdn.com/v4/letter/p/f6c823/32.png) [@prophoto](https://discuss.elastic.co/u/prophoto)\
**Post date:** [November 25, 2017, 5:24pm UTC](https://discuss.elastic.co/t/should-i-move-es-to-docker/109110/1 "2017-11-25T17:24:30Z")

</div>

I have ES 5.3 and Logstash 5.3 installed on a Centos 7 VM. Lately I've started using Docker for more projects and starting to like it. I need to move ES off of the current host machine onto another so I can use it for another project. It would be easy to just install CentOS 7 on another machine and move data, but should I bother with putting it in a docker image and run everything on the same docker host? I'm running everything on hyperv core. Thanks!

---

<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:** [November 25, 2017, 7:06pm UTC](https://discuss.elastic.co/t/should-i-move-es-to-docker/109110/2 "2017-11-25T19:06:24Z")

</div>

I think this really comes down to personal choice.

I would, it makes upgrades easier 😉

---

<div class="post-metadata">

**Author:** ![prophoto](https://avatars.discourse-cdn.com/v4/letter/p/f6c823/32.png) [@prophoto](https://discuss.elastic.co/u/prophoto)\
**Post date:** [November 25, 2017, 7:55pm UTC](https://discuss.elastic.co/t/should-i-move-es-to-docker/109110/3 "2017-11-25T19:55:45Z")

</div>

Is there a guide to migrate to Docker?

---

<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:** [November 25, 2017, 8:10pm UTC](https://discuss.elastic.co/t/should-i-move-es-to-docker/109110/4 "2017-11-25T20:10:44Z")

</div>

Nope, it's simply a containerisation method so we don't treat it any different to if you were moving to/from VMs.

Options are;

1. Snapshot and restore
2. Add the docker node to the existing cluster, move data over to it with allocation filtering, then remove the old node(s)

---

<div class="post-metadata">

**Author:** ![prophoto](https://avatars.discourse-cdn.com/v4/letter/p/f6c823/32.png) [@prophoto](https://discuss.elastic.co/u/prophoto)\
**Post date:** [November 25, 2017, 8:55pm UTC](https://discuss.elastic.co/t/should-i-move-es-to-docker/109110/5 "2017-11-25T20:55:49Z")

</div>

I'll research both, thanks! How about upgrading to ES6 while I'm at it? Can I add an es6 to existing 5.3 single unit cluster?

---

<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:** [November 25, 2017, 8:58pm UTC](https://discuss.elastic.co/t/should-i-move-es-to-docker/109110/6 "2017-11-25T20:58:39Z")

</div>

You will need to upgrade to 5.6.4, but then you can!

---

<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 23, 2017, 8:59pm UTC](https://discuss.elastic.co/t/should-i-move-es-to-docker/109110/7 "2017-12-23T20:59:37Z")

</div>

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