# Config separate container to different host

**URL:** <https://forums.suse.com/t/config-separate-container-to-different-host/3935>\
**Category:** Rancher 1.x\
**Created:** [September 8, 2016, 2:23pm UTC](https://forums.suse.com/t/config-separate-container-to-different-host/3935 "2016-09-08T14:23:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![RotemEmergi](https://avatars.discourse-cdn.com/v4/letter/r/e5b9ba/32.png) [@RotemEmergi](https://forums.suse.com/u/RotemEmergi)\
**Post date:** [September 8, 2016, 2:23pm UTC](https://forums.suse.com/t/config-separate-container-to-different-host/3935/1 "2016-09-08T14:23:12Z")

</div>

Hi ,

There is a way mabay that I can put a flag in the docker-compose for config container to build in different host ?

Best regards

---

<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:** [September 8, 2016, 9:41pm UTC](https://forums.suse.com/t/config-separate-container-to-different-host/3935/2 "2016-09-08T21:41:35Z")

</div>

I’m not completely sure what you’re trying to do, but you can always schedule your containers to be on different hosts.

[http://docs.rancher.com/rancher/v1.2/en/cattle/scheduling/](http://docs.rancher.com/rancher/v1.2/en/cattle/scheduling/)

---

<div class="post-metadata">

**Author:** ![nma](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/nma/32/1332_2.png) [@nma](https://forums.suse.com/u/nma)\
**Post date:** [September 8, 2016, 9:53pm UTC](https://forums.suse.com/t/config-separate-container-to-different-host/3935/3 "2016-09-08T21:53:37Z")

</div>

The person who setup our Rancher treated his hosts like Pets. So we have 3 Rancher Hosts in House  
like so:

 ![](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/6/660ea3e8ae920e98d304418bb714dd6f9a50765d.png)

We kept different configurations that we mounted to our containers on them, so some of our dev containers must be on gondolin and etc.

```auto
labels:
    io.rancher.container.network: 'true' 
    io.rancher.scheduler.affinity:host_label: name=gondolin

```

You can also specify this on the UI. Though I recommend docker-compose files for easy tracking.