# Support Docker v0.9.1 and up

**URL:** <https://meta.discourse.org/t/support-docker-v0-9-1-and-up/15154>\
**Category:** Feature\
**Created:** [2014 年 4 月 29 日午前 8:49 UTC](https://meta.discourse.org/t/support-docker-v0-9-1-and-up/15154 "2014-04-29T08:49:08Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![stealthii](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stealthii/32/122550_2.png) [@stealthii](https://meta.discourse.org/u/stealthii)\
**Post date:** [2014 年 4 月 29 日午前 8:49 UTC](https://meta.discourse.org/t/support-docker-v0-9-1-and-up/15154/1 "2014-04-29T08:49:08Z")

</div>

Ubuntu 14.04 LTS ships with Docker v0.9.1, as the package `docker.io`. The launcher script asks for v0.10.x or above, yet Discourse runs fine under the official docker release by Ubuntu.

I would like to think that 14.04.1 provides a vendor upgrade to Docker 1.0, but for now [docker.io](http://docker.io) does not provide [specific instructions for upsteam releases on 14.04](http://docs.docker.io/installation/ubuntulinux/). A few Docker cloud providers are beginning their Docker deployment on 14.04 hosts with the vendor supported version of Docker.

If we can avoid breaking support for Docker v0.9.1 in the meantime, I see no reason to have the script allow v0.9.1 and up. A solution is to warn the user about upgrading, rather than terminating the script.

* * *

I mistakenly posted this under [Github issues](https://github.com/discourse/discourse_docker/issues/39) rather than here. @supermathie commented that as Docker is still new and [moving so quickly](https://github.com/dotcloud/docker/blob/master/CHANGELOG.md), encouragement to stay on the latest version is a good thing. @sam mentioned about [a possible regression](https://github.com/dotcloud/docker/issues/5106#issuecomment-39931853) for his reason for not supporting v0.9.1.

---

_[View the full topic](https://meta.discourse.org/t/support-docker-v0-9-1-and-up/15154)._