As we saw multiple times in earlier chapters, IPAM is a critical component of any container networking solution. The criticality of IPAM becomes even clearer when you start using common networks across multiple Docker hosts. As the number of IP allocations begins to scale being able to resolve these containers by names also becomes vital. Much like Docker, Weave has its own integrated IPAM for their container network solution. In this chapter, we'll show how to configure and leverage Weave IPAM to manage IP allocations across the Weave network.
It is assumed that you're building off of the lab we created in the first recipe of this chapter. It is also assumed that the hosts have Docker and Weave installed. Docker should be in its default configuration, and Weave should be installed but not yet peered. If you need to remove the peering defined in previous examples, issue the weave reset command on each host.