# Docker Compose v3

**URL:** <https://forums.suse.com/t/docker-compose-v3/5444>\
**Category:** Rancher 1.x\
**Created:** [February 7, 2017, 5:30pm UTC](https://forums.suse.com/t/docker-compose-v3/5444 "2017-02-07T17:30:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![andersonbn](https://avatars.discourse-cdn.com/v4/letter/a/c6cbf5/32.png) [@andersonbn](https://forums.suse.com/u/andersonbn)\
**Post date:** [February 7, 2017, 5:30pm UTC](https://forums.suse.com/t/docker-compose-v3/5444/1 "2017-02-07T17:30:18Z")

</div>

Docker compose v3 is out and with it are gone all the constraint options (cpu\_shares, cpu\_quota, cpuset, mem\_limit, memswap\_limit), which have been moved to the new “deploy” section, for better integration with Docker Swarm (see [here](https://docs.docker.com/compose/compose-file/#/version-3)).  
Since the scheduler takes into account both memoryReservation and milliCpuReservation fields for deciding container allocation in the hosts, should I worry about these old (but still current) docker compose options not being supported by Rancher in future versions?

---

<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:** [February 7, 2017, 6:06pm UTC](https://forums.suse.com/t/docker-compose-v3/5444/2 "2017-02-07T18:06:14Z")

</div>

Reservations are Rancher options for making scheduling decisions and unrelated to the runtime options in the docker engine for limiting the resources the container can actually take.