Docker: how to connect two bridges
Solution 1
You can try making use of the veth peer so that you can connect two bridges. Make sure you are rename and names respectively with the one you configured.
ip link add veth0 type veth peer name veth1
ifconfig veth0 up
ifconfig veth1 up
brctl addif <D1-A-Bridge> veth0
brctl addif <D2-A-Bridge> veth1
Solution 2
To connect container2 to container1 you can also connect it to bridgeB
$ docker network connect bridgeB container1
This will allow container1 to connect to container2 by IP address, DNS names would still have to be updated manually afaik.
More information in the Docker networking guide here.
hawarden_
Updated on June 04, 2022Comments
-
hawarden_ almost 2 years
As you know after Docker 1.9 we can create bridges to connect containers.
I have created two custom bridges: bridge A
172.18.0.1
and bridge B172.19.0.1
.Now I have a container1 on bridge A, and a container2 on bridge B called "mailServer".
The container1 needs to reach container2 by a DNS, how should I do this? Because they are on different bridges so they cannot talk to each other. Do I need a router and can I achieve this by Docker?
This is a new feature of Docker and I didn't find much information. Thanks.
-
Sida Zhou over 5 yearsIs there a more semantic way to connect two custom bridge networks?
docker network connect NETWORK1 NETWORK2
is not supported. Is connecting two custom bridge networks bad idea (might be bad idea since it's not supported)? Why? -
focus zheng about 3 yearsif Bridge A and Bridge B is not in a same subnet.the connection is not useful.