Custom bridge network for containers

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.

At this moment, we don’t support the networks directive in docker-compose, see this issue here: 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.