# Roadmap for Docker 1.10/Compose 1.6 **URL:** \ **Category:** Rancher 1.x\ **Created:** [February 5, 2016, 7:50am UTC](https://forums.suse.com/t/roadmap-for-docker-1-10-compose-1-6/1643 "2016-02-05T07:50:44Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![johnrengelman](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/johnrengelman/32/134_2.png) [@johnrengelman](https://forums.suse.com/u/johnrengelman)\ **Post date:** [February 5, 2016, 7:50am UTC](https://forums.suse.com/t/roadmap-for-docker-1-10-compose-1-6/1643/1 "2016-02-05T07:50:45Z")
Docker 1.10 and Compose 1.6 were release today and Compose introduces a new file format. One of the leading sealing points for Rancher for me when dealing with clients is that a single `docker-compose.yml` file can be used to run both locally and submitted to the Rancher cluster to run. What are the plans for supporting the new file syntax ([https://blog.docker.com/2016/02/compose-1-6](https://blog.docker.com/2016/02/compose-1-6))? Are there also any plans to support the new `network` and `volume` sections of the file (not quite sure how that would work with Rancher’s networking and storage systems). ---
**Author:** ![pwFoo](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/pwfoo/32/2884_2.png) [@pwFoo](https://forums.suse.com/u/pwFoo)\ **Post date:** [February 5, 2016, 8:16pm UTC](https://forums.suse.com/t/roadmap-for-docker-1-10-compose-1-6/1643/2 "2016-02-05T20:16:16Z")
Would be great to get the new Docker 1.10 network features with Rancher / RancherOS. Following here… ---
**Author:** ![deitch](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/deitch/32/40_2.png) [@deitch](https://forums.suse.com/u/deitch)\ **Post date:** [February 7, 2016, 4:20pm UTC](https://forums.suse.com/t/roadmap-for-docker-1-10-compose-1-6/1643/3 "2016-02-07T16:20:03Z")
Ditto. The new file format is quite powerful. When will Rancher support it? ---
**Author:** ![deitch](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/deitch/32/40_2.png) [@deitch](https://forums.suse.com/u/deitch)\ **Post date:** [February 8, 2016, 12:57pm UTC](https://forums.suse.com/t/roadmap-for-docker-1-10-compose-1-6/1643/4 "2016-02-08T12:57:18Z")
Add in the ability to define networks on the fly, and I just realized it is really important to us ---
**Author:** ![ibuildthecloud](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/ibuildthecloud/32/8_2.png) [@ibuildthecloud](https://forums.suse.com/u/ibuildthecloud)\ **Post date:** [February 8, 2016, 5:09pm UTC](https://forums.suse.com/t/roadmap-for-docker-1-10-compose-1-6/1643/5 "2016-02-08T17:09:50Z")
RancherOS w/ Docker 1.10 should be released this week (cross your fingers). RancherOS always support all of Docker’s features so 1.10 network will work fine there. For Rancher we will be adding the 1.6 compose v2 format shortly. There is a lot of question on our side of what “networks” really mean in the context of Rancher. It will take a bit longer to sort that out. Unfortunately the Docker “network” concept does not align with what many users think a network is, but it is really more focused on service discovery. From a design perspective we are still struggling with that. Volumes in 1.10 haven’t really changed, except the new compose format, so they will work fine in Rancher. ---
**Author:** ![pwFoo](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/pwfoo/32/2884_2.png) [@pwFoo](https://forums.suse.com/u/pwFoo)\ **Post date:** [February 9, 2016, 5:43am UTC](https://forums.suse.com/t/roadmap-for-docker-1-10-compose-1-6/1643/6 "2016-02-09T05:43:44Z")
Routed networking and static assigned ip addresses are great and needed features. Rancher should support docker networking, but could also use the own network solution / plugin. Routed subnet feature should be added. Tested docker 1.10 by deploy the rancher docker image and an upgraded RancherOS to the lattest dev / prerelease and it works fine (native docker networking).