# Custom bridge network for containers

**URL:** <https://forums.suse.com/t/custom-bridge-network-for-containers/6465>\
**Category:** Rancher 1.x\
**Created:** [May 25, 2017, 1:15pm UTC](https://forums.suse.com/t/custom-bridge-network-for-containers/6465 "2017-05-25T13:15:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michal.Jusik](https://avatars.discourse-cdn.com/v4/letter/m/9dc877/32.png) [@Michal.Jusik](https://forums.suse.com/u/Michal.Jusik)\
**Post date:** [May 25, 2017, 1:15pm UTC](https://forums.suse.com/t/custom-bridge-network-for-containers/6465/1 "2017-05-25T13:15:11Z")

</div>

Hi ,

Our applications stack uses “networks” key word in docker-compose.yml.  
This allows to create multiply environment which are independent.  
Each one uses the same hostnames which simplifies the image creation.

Docker-compose looks like this :  
(Of course names and path were replaced in this example.)

version: '2’  
services:  
srv1:  
image: {registry}/srv1:master  
privileged: true  
volumes:  
- /opt/tools/su:/etc/pam.d/su  
command: bash -c "{path-to-start-script}"  
srv2:  
image: {registry}/srv2:master  
environment:  
- TYPE=hypervisor  
- HYP\_PORT=1234  
ports:  
- “9943:443”  
- "1234:1234"  
networks:  
inside:  
aliases:  
- dmgr.local  
command: bash -c "{path-to-start-script}

networks:  
inside:

The question is how can I create custom bridge networks like in the example “inside” ?  
Is it possible to do that with Rancher ?

If I launch stack using docker-compose up -d then of course docker creates proper bridge networks which are visible at Cattle on “Container-name” -\> “Networking” tab.

---

<div class="post-metadata">

**Author:** ![superseb](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/superseb/32/2424_2.png) [@superseb](https://forums.suse.com/u/superseb)\
**Post date:** [June 29, 2017, 8:30am UTC](https://forums.suse.com/t/custom-bridge-network-for-containers/6465/2 "2017-06-29T08:30:57Z")

</div>

At this moment, we don’t support the networks directive in docker-compose, see this issue here: [https://github.com/rancher/rancher/issues/5715](https://github.com/rancher/rancher/issues/5715). Please upvote (using the thumbs up emoji on the first post of the issue) the issue if you need this, so we can use this in prioritising.