The recipes until this point have shown several possibilities for what's possible when manually configuring Docker networks. Although these are all possible solutions, they all require a fair amount of manual intervention and configuration and are not easily consumable in their current form. If we use the previous recipe as an example, there are a few notable drawbacks:
You are responsible for keeping track of IP allocations on the containers increasing your risk of assigning conflicting IP addresses to different containers
There is no dynamic port mapping or inherent outbound masquerading to facilitate communication between a container and the rest of the network
While we used Pipework to lessen the configuration burden, there was still a fair amount of manual configuration that needed to be done to connect a container to the OVS bridge
The majority of the configuration would not persist through a host reboot by default
This being said, using what we've learned so far...