# Docker version on the host

**URL:** https://forums.suse.com/t/docker-version-on-the-host/573
**Category:** Rancher 1.x
**Created:** [September 28, 2015, 12:23pm UTC](https://forums.suse.com/t/docker-version-on-the-host/573 "2015-09-28T12:23:23Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![ebishop](https://avatars.discourse-cdn.com/v4/letter/e/9dc877/32.png) [@ebishop](https://forums.suse.com/u/ebishop)
#### Post date: [September 28, 2015, 12:23pm UTC](https://forums.suse.com/t/docker-version-on-the-host/573/1 "2015-09-28T12:23:23Z")

</div>

What is the plan for managing host upgrades? When we up grade to new versions of the Rancher server, are the rancher agents automatically updated as well?

And then the question of backward compatibility comes to mind. How old it too old when it comes to the Docker engine running on the hosts?

---

<div class="post-metadata">

### Author: ![vincent](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vincent/32/7156_2.png) [@vincent](https://forums.suse.com/u/vincent)
#### Post date: [September 28, 2015, 3:53pm UTC](https://forums.suse.com/t/docker-version-on-the-host/573/2 "2015-09-28T15:53:30Z")

</div>

Agents are automatically upgraded when `rancher/server` is. The Docker daemon itself is not managed so you upgrade it through your OS (RancherOS releases generally include the latest version, though we’re behind in getting 0.4 out).

Docker 1.6+ is [currently required](https://github.com/rancher/rancher/blob/master/README.md#requirements), if that changes (and it likely will for network drivers soon) it will be noted in the release notes.

---

<div class="post-metadata">

### Author: ![ebishop](https://avatars.discourse-cdn.com/v4/letter/e/9dc877/32.png) [@ebishop](https://forums.suse.com/u/ebishop)
#### Post date: [September 28, 2015, 6:40pm UTC](https://forums.suse.com/t/docker-version-on-the-host/573/3 "2015-09-28T18:40:08Z")

</div>

Support back to 1.6+ is plenty. I was only hoping for n-1 🙂
