# Rancher CLI up command error - no such service

**URL:** <https://forums.suse.com/t/rancher-cli-up-command-error-no-such-service/7375>\
**Category:** Rancher 1.x\
**Created:** [September 20, 2017, 5:57pm UTC](https://forums.suse.com/t/rancher-cli-up-command-error-no-such-service/7375 "2017-09-20T17:57:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sundevil](https://avatars.discourse-cdn.com/v4/letter/s/3d9bf3/32.png) [@sundevil](https://forums.suse.com/u/sundevil)\
**Post date:** [September 20, 2017, 5:57pm UTC](https://forums.suse.com/t/rancher-cli-up-command-error-no-such-service/7375/1 "2017-09-20T17:57:09Z")

</div>

Using the Rancher CLI. I can run commands like ‘rancher restart mystack/myservice’ and ‘rancher inspect mystack/myservice’, but when i run ‘rancher up mystack/myservice’ i get a message “no such service”. am I doing something wrong, or is this a CLI bug? Have tried various options on the up command, such as -s to specify stack, but always get same result. Rancher Version installed is 1.6.5.

I want to use CLI, to upgrade a service to a newer image, so really need this to work.

---

<div class="post-metadata">

**Author:** ![sundevil](https://avatars.discourse-cdn.com/v4/letter/s/3d9bf3/32.png) [@sundevil](https://forums.suse.com/u/sundevil)\
**Post date:** [September 20, 2017, 6:43pm UTC](https://forums.suse.com/t/rancher-cli-up-command-error-no-such-service/7375/2 "2017-09-20T18:43:26Z")

</div>

apparently it requires the docker-compose.yml and rancher-compose.yml files, then it works.