# Remove sidekick from existing service

**URL:** <https://forums.suse.com/t/remove-sidekick-from-existing-service/4504>\
**Category:** Rancher 1.x\
**Created:** [October 31, 2016, 7:20pm UTC](https://forums.suse.com/t/remove-sidekick-from-existing-service/4504 "2016-10-31T19:20:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidnortonjr](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/davidnortonjr/32/1827_2.png) [@davidnortonjr](https://forums.suse.com/u/davidnortonjr)\
**Post date:** [October 31, 2016, 7:20pm UTC](https://forums.suse.com/t/remove-sidekick-from-existing-service/4504/1 "2016-10-31T19:20:06Z")

</div>

Hi, I have an existing service with a sidekick. I’ve updated my application to no longer require the sidekick, so I removed the sidekick from the docker-compose and rancher-compose files. However, the rancher-compose CLI does not delete the sidekick - the container remains running and it still shows up under View Config

Is there a way (UI or CLI) to break that relationship and delete the legacy sidekick?

Rancher 1.1.4 with Cattle.

Thank you!

---

<div class="post-metadata">

**Author:** ![ampedandwired](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/ampedandwired/32/1721_2.png) [@ampedandwired](https://forums.suse.com/u/ampedandwired)\
**Post date:** [November 1, 2016, 3:21am UTC](https://forums.suse.com/t/remove-sidekick-from-existing-service/4504/2 "2016-11-01T03:21:15Z")

</div>

We’ve had problems with this also. Adding a new sidekick to an existing service that already has sidekicks doesn’t work either.
