minidcos docker create --network creates clusters with nodes having two bridge networks.

[crakensio]

Docker network created with custom network configs.

docker network create -d bridge --internal --subnet=192.170.3.0/24 --ip-range=192.170.3.0/24 --gateway=192.170.3.1 --opt com.docker.network.bridge.name=eth4 cusnet
minidcos command used to create the cluster

minidcos docker create path/dcos_generate_config.sh --network cusnet --cluster-id Clustername --genconf-dir path/custom-genconf

Config: 1 Master, 1 Public , 2 Agent Node.

All the containers are deployed. Each container is associated with default bridge network(docker0) and custom network(cusnet)

DCOS is picking docker0 Network IP for all the containers and not using custom network.

minidcos, version 2019.04.08.1
Docker version 18.06.3-ce, build d7080c1

[timaa2k]

Does your custom genconf dir include an IP detect script which points to the eth1 instead of eth0?

…

Am 24.07.2019 um 20:57 schrieb sarathkumar ***@***.***>: Docker network created with custom network configs. docker network create -d bridge --internal --subnet=192.170.3.0/24 --ip-range=192.170.3.0/24 --gateway=192.170.3.1 --opt com.docker.network.bridge.name=eth4 cusnet minidcos command used to create the cluster minidcos docker create path/dcos_generate_config.sh --network cusnet --cluster-id Clustername --genconf-dir path/custom-genconf Config: 1 Master, 1 Public , 2 Agent Node. All the containers are deployed. Each container is associated with default bridge network(docker0) and custom network(cusnet) DCOS is picking docker0 Network IP for all the containers and not using custom network. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[timaa2k]

https://minidcos.readthedocs.io/en/latest/dcos-docker-cli.html#using-a-custom-docker-network You need to use the IP detect script presented here.

…

Am 24.07.2019 um 20:57 schrieb sarathkumar ***@***.***>: Docker network created with custom network configs. docker network create -d bridge --internal --subnet=192.170.3.0/24 --ip-range=192.170.3.0/24 --gateway=192.170.3.1 --opt com.docker.network.bridge.name=eth4 cusnet minidcos command used to create the cluster minidcos docker create path/dcos_generate_config.sh --network cusnet --cluster-id Clustername --genconf-dir path/custom-genconf Config: 1 Master, 1 Public , 2 Agent Node. All the containers are deployed. Each container is associated with default bridge network(docker0) and custom network(cusnet) DCOS is picking docker0 Network IP for all the containers and not using custom network. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[timaa2k]

Given your setup you may need to change the script to eth4 though.

…

Am 24.07.2019 um 20:57 schrieb sarathkumar ***@***.***>: Docker network created with custom network configs. docker network create -d bridge --internal --subnet=192.170.3.0/24 --ip-range=192.170.3.0/24 --gateway=192.170.3.1 --opt com.docker.network.bridge.name=eth4 cusnet minidcos command used to create the cluster minidcos docker create path/dcos_generate_config.sh --network cusnet --cluster-id Clustername --genconf-dir path/custom-genconf Config: 1 Master, 1 Public , 2 Agent Node. All the containers are deployed. Each container is associated with default bridge network(docker0) and custom network(cusnet) DCOS is picking docker0 Network IP for all the containers and not using custom network. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[crakensio]

@timaa2k Thanks but my script does include ip-detect script and I change the network adaptor in the ip-detect script to the network adaptor I mentioned while creating the custom network.

[crakensio]

Could anyone help me with this issues?