Our application is a combination of 4 different applications. The graphics part is running on a host and other 3 applications are running on 3 different VMs. Which uses bridge networking.
eg. Graphics app1 - 192.168.2.201 (Base Machine/HOST)
Application 2 - 192.168.2.202 (VM1)
Application 3 - 192.168.2.203 (VM2)
Application 4 - 192.168.2.204 (VM3)
Which is running fine.
But, to get advantage of containers, we want to shift our VM applications into docker container. But in docker, when we are using Bridge Networking, it doesn't take IPs in HOST network, obviously because, Bridge network ID is not same as host. And application fails to run.
How can we achieve the Bridge Networking with same network ID (say 192.168.2.0)? We cannot use Host networking.
Note: our application specifically wants IP in 192.168.2.0 network, otherwise it fails.
wants IP in 192.168.2.0 network
? Is it hardcoded in the software? Would it be possible to change the code? – 030 Jan 12 '19 at 15:39