# Docker 1.11 Supported only?

**URL:** <https://discuss.elastic.co/t/docker-1-11-supported-only/72033>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [January 18, 2017, 3:21pm UTC](https://discuss.elastic.co/t/docker-1-11-supported-only/72033 "2017-01-18T15:21:22Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![kitsushadow](https://avatars.discourse-cdn.com/v4/letter/k/a87d85/32.png) [@kitsushadow](https://discuss.elastic.co/u/kitsushadow)\
**Post date:** [January 18, 2017, 3:21pm UTC](https://discuss.elastic.co/t/docker-1-11-supported-only/72033/1 "2017-01-18T15:21:23Z")

</div>

I work in the Federal space which requires flexibility in the versions of docker that are used. Officially 1.10.2 is the current supported version but we need to be able to test against many versions of docker including the beta releases. currently , the install only supports docker 1.11. Could the force check fail be removed in favor of a warning stating that the version of ECE supports docker 1.11? This shouldn't make debugging and support that difficult.

Currently it's not possible to test this product in our secure environment where its most important if we wish to evaluate it.

Thanks

---

<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:** [January 21, 2017, 3:21pm UTC](https://discuss.elastic.co/t/docker-1-11-supported-only/72033/2 "2017-01-21T15:21:26Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![nrichers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nrichers/32/17801_2.png) [@nrichers](https://discuss.elastic.co/u/nrichers)\
**Post date:** [January 23, 2017, 11:23pm UTC](https://discuss.elastic.co/t/docker-1-11-supported-only/72033/3 "2017-01-23T23:23:50Z")

</div>



---

<div class="post-metadata">

**Author:** ![nrichers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nrichers/32/17801_2.png) [@nrichers](https://discuss.elastic.co/u/nrichers)\
**Post date:** [January 24, 2017, 12:12am UTC](https://discuss.elastic.co/t/docker-1-11-supported-only/72033/4 "2017-01-24T00:12:26Z")

</div>

@kitsushadow,

My apologies, your post was auto-closed without receiving a reply. I reopened it and relayed your question to our team. I hope that one of them can chime in.

Nik

---

<div class="post-metadata">

**Author:** ![kitsushadow](https://avatars.discourse-cdn.com/v4/letter/k/a87d85/32.png) [@kitsushadow](https://discuss.elastic.co/u/kitsushadow)\
**Post date:** [January 24, 2017, 12:38am UTC](https://discuss.elastic.co/t/docker-1-11-supported-only/72033/5 "2017-01-24T00:38:53Z")

</div>

Thanks

---

<div class="post-metadata">

**Author:** ![uricohen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/uricohen/32/9776_2.png) [@uricohen](https://discuss.elastic.co/u/uricohen)\
**Post date:** [January 24, 2017, 12:50am UTC](https://discuss.elastic.co/t/docker-1-11-supported-only/72033/6 "2017-01-24T00:50:09Z")

</div>

Hi @kitsushadow

Currently we indeed check for a specific Docker version, due to having issues with rogue Docker versions in the past. So we wanted to ensure users are running on a Docker version that we know to be working well with Elastic Cloud Enterprise. That said, I can see your point, and we'll consider adding a force override flag or something along those lines for one of the upcoming releases.

Thanks for you input!  
Uri

---

<div class="post-metadata">

**Author:** ![kitsushadow](https://avatars.discourse-cdn.com/v4/letter/k/a87d85/32.png) [@kitsushadow](https://discuss.elastic.co/u/kitsushadow)\
**Post date:** [January 24, 2017, 9:14am UTC](https://discuss.elastic.co/t/docker-1-11-supported-only/72033/7 "2017-01-24T09:14:40Z")

</div>

Thanks for the response and consideration of the feature, it will definitely help us and others out.

---

<div class="post-metadata">

**Author:** ![m-kiuchi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/m-kiuchi/32/15219_2.png) [@m-kiuchi](https://discuss.elastic.co/u/m-kiuchi)\
**Post date:** [February 6, 2017, 2:23am UTC](https://discuss.elastic.co/t/docker-1-11-supported-only/72033/8 "2017-02-06T02:23:18Z")

</div>

Docker provides "Commercially Supported" version. Is there any plan to use it, or Elastic provides commercial support including Docker Engine itself ?

[https://docs.docker.com/cs-engine/release-notes/release-notes/](https://docs.docker.com/cs-engine/release-notes/release-notes/)

---

<div class="post-metadata">

**Author:** ![uricohen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/uricohen/32/9776_2.png) [@uricohen](https://discuss.elastic.co/u/uricohen)\
**Post date:** [February 6, 2017, 10:07am UTC](https://discuss.elastic.co/t/docker-1-11-supported-only/72033/9 "2017-02-06T10:07:27Z")

</div>

Hi @m-kiuchi

We use the open source version of Docker Engine. We will provide support for Elastic Cloud Enterprise, and naturally that may involve troubleshooting issues that may be related to Docker itself. Naturally, that doesn't mean we will provide generic support for Docker.

HTH  
Uri

---

<div class="post-metadata">

**Author:** ![m-kiuchi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/m-kiuchi/32/15219_2.png) [@m-kiuchi](https://discuss.elastic.co/u/m-kiuchi)\
**Post date:** [February 7, 2017, 1:34am UTC](https://discuss.elastic.co/t/docker-1-11-supported-only/72033/10 "2017-02-07T01:34:18Z")

</div>

Thanks, Uri.

MK

---

<div class="post-metadata">

**Author:** ![pmoust](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pmoust/32/11656_2.png) [@pmoust](https://discuss.elastic.co/u/pmoust)\
**Post date:** [February 20, 2017, 4:30pm UTC](https://discuss.elastic.co/t/docker-1-11-supported-only/72033/11 "2017-02-20T16:30:12Z")

</div>


