# Rancher-compose up hangs when sidekicks defined

**URL:** <https://forums.suse.com/t/rancher-compose-up-hangs-when-sidekicks-defined/961>\
**Category:** Rancher 1.x\
**Created:** [November 16, 2015, 11:38am UTC](https://forums.suse.com/t/rancher-compose-up-hangs-when-sidekicks-defined/961 "2015-11-16T11:38:48Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kiboro](https://avatars.discourse-cdn.com/v4/letter/k/7993a0/32.png) [@kiboro](https://forums.suse.com/u/kiboro)\
**Post date:** [November 16, 2015, 11:38am UTC](https://forums.suse.com/t/rancher-compose-up-hangs-when-sidekicks-defined/961/1 "2015-11-16T11:38:48Z")

</div>

I have the following docker-compose file. As it stands it works just fine. However if I uncomment the sidekick label then rancher-compose simply hangs, no output, nothing shown in Rancher UI. Rancher-compose 0.5.1

```auto
cmm:
 image: docker.pibenchmark.com/contract-management-api:0.0.30
 description: Contract Management Module
 environment:
  EUREKA_CLIENT_SERVICEURL_DEFAULT_ZONE: http://eureka:8761/eureka/
  SPRING_PROFILES_ACTIVE: ranchertest
 external_links:
 - infrastructure/keycloak:keycloak
 - infrastructure/eureka:eureka
 links:
 - cmm-data:mongodb
# labels:
# io.rancher.sidekicks: cmm-data
 tty: true
 stdin_open: true
cmm-data:
  image: mongo
  volumes:
  - cmm-data:/data/db
  volume_driver: convoy

```

---

<div class="post-metadata">

**Author:** ![kiboro](https://avatars.discourse-cdn.com/v4/letter/k/7993a0/32.png) [@kiboro](https://forums.suse.com/u/kiboro)\
**Post date:** [November 16, 2015, 2:42pm UTC](https://forums.suse.com/t/rancher-compose-up-hangs-when-sidekicks-defined/961/2 "2015-11-16T14:42:58Z")

</div>

I’v just proved definitively that sidekicks are mutually exclusive with links. Shame as I wanted to make my databases sidekicks of the services for tidiness. Is there a reason why this is so?

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [November 19, 2015, 6:15pm UTC](https://forums.suse.com/t/rancher-compose-up-hangs-when-sidekicks-defined/961/3 "2015-11-19T18:15:53Z")

</div>

Yes, you cannot link with a sidekick, but in your use case, I think you are looking for this enhancement. This would allow you to remove the links and the environment variables that are typically taken care of through the “links” would be automatically done for sidekicks.

> <https://github.com/rancher/rancher/issues/1589>
>
> Rancher: v0.28.0
> Cattle: v0.64.0
> Rancher-compose: v0.22.0
> With the following docker-compose.yml:
> test-apache:
> ports:
> - 80:80/tcp
> restart: on-failure:5
> tty: true
> image: debian:jessie
> links:
> - test-node:node
> stdin\_open: true
> test-node:
> ...

---

<div class="post-metadata">

**Author:** ![kiboro](https://avatars.discourse-cdn.com/v4/letter/k/7993a0/32.png) [@kiboro](https://forums.suse.com/u/kiboro)\
**Post date:** [November 19, 2015, 6:57pm UTC](https://forums.suse.com/t/rancher-compose-up-hangs-when-sidekicks-defined/961/4 "2015-11-19T18:57:39Z")

</div>

That would be ideal. In essence a sidekick would be transparently linked. It’s really only for tidiness in the UI. Se have a number of services which use a private database which doesn’t need to visually be a whole separate service.
