# Rancher CLI vs Rancher-compose

**URL:** <https://forums.suse.com/t/rancher-cli-vs-rancher-compose/5811>\
**Category:** Rancher 1.x\
**Created:** [March 10, 2017, 3:20pm UTC](https://forums.suse.com/t/rancher-cli-vs-rancher-compose/5811 "2017-03-10T15:20:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cabrinoob](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/cabrinoob/32/1343_2.png) [@cabrinoob](https://forums.suse.com/u/cabrinoob)\
**Post date:** [March 10, 2017, 3:20pm UTC](https://forums.suse.com/t/rancher-cli-vs-rancher-compose/5811/1 "2017-03-10T15:20:08Z")

</div>

What are the main differences between Rancher CLI (beta) and rancher compose tool?

In the documentation I can read :

> The Rancher Compose tool works just like the popular Docker Compose and supports the V1 version of docker-compose.yml files.

Does it means that in v1.4.1 of rancher and its “version 2” of docker-compose, we have to use Rancher CLI instead of Rancher Compose ?

Thank you

---

<div class="post-metadata">

**Author:** ![Tomas\_Holcman](https://avatars.discourse-cdn.com/v4/letter/t/a88e4f/32.png) [@Tomas\_Holcman](https://forums.suse.com/u/Tomas_Holcman)\
**Post date:** [March 15, 2017, 2:08am UTC](https://forums.suse.com/t/rancher-cli-vs-rancher-compose/5811/2 "2017-03-15T02:08:49Z")

</div>

I am curious too. What is preferred way how to manage Rancher from CLI?

---

<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:** [March 15, 2017, 5:45am UTC](https://forums.suse.com/t/rancher-cli-vs-rancher-compose/5811/3 "2017-03-15T05:45:09Z")

</div>

Both support compose v1 and v2 syntax. Rancher-compose deals only with stacks and services, the newer CLI has almost all the same functionality and does hosts and other things too. Once the last few missing things have been addressed or deprecated, rancher-compose itself will be deprecated.
