This can be run manually, or by an orchestrator. In Docker, networks are created using the docker network create command. In this post, we will focus on Docker, with a later post showing similar functionality using CNI. The Docker container networking model (CNM), and the competing Container Network Interface (CNI), enable the creation and management of these networks to serve all of these use cases and more. Alternately, you may have pre-defined networks or VLANs within your environment to which you would like to attach containers. If each microservice has its own subnet, this can also simplify any security rules used to control traffic between microservices. You can also create a common shared network across multiple hosts of cooperating applications and associated microservices. You can create separate networks for different microservices based applications across multiple-hosts that do not need to interact, therefore isolating the traffic between containers.
![docker network inside outside docker network inside outside](https://hlassets.paessler.com/common/files/blog/2016/docker_container_status.png)
![docker network inside outside docker network inside outside](https://docs.docker.com/engine/tutorials/bridge1.png)
Near the end, we will build a real example of a 3 node cluster configured to share a network. Our focus in this post is around the User Defined Network and more specifically the bridge type.
#DOCKER NETWORK INSIDE OUTSIDE DRIVER#
In this paper we examine the details of the Infoblox Docker IPAM driver for specific use cases and including command syntax.
![docker network inside outside docker network inside outside](https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/media/windowsnetworkstack-simple.png)
In a complex container deployment is important to have a service like Infoblox IPAM to help maintain consistency in a very dynamic multi-host environment dealing with IP address and network creation and deletions. Docker requires the services of an IPAM infrastructure to enable the creation of network address spaces/pools, subnets and the allocation of individual IP addresses for the container-based microservices. As you saw in my previous blog How Docker Networking Works and the Importance of IPAM Functionality, Docker’s networking model enables 3rd party vendors to ‘plug-in’ enterprise class network solutions.