1.6 KiB
title, menu_order
| title | menu_order |
|---|---|
| How the Weave Net Docker Network Plugin Works | 20 |
The Weave Net plugin actually provides two network drivers to Docker - one named weavemesh that can operate without a cluster store and another one named weave that can only work with one (like Docker's overlay driver).
weavemesh driver
- Weave Net handles all co-ordination between hosts (referred to by Docker as a "local scope" driver)
- Supports a single network only. A network named
weaveis automatically created for you. - Uses Weave Net's partition tolerant IPAM
If you do create additional networks using the weavemesh driver, containers attached to them will be able to communicate with containers attached to weave. There is no isolation between those networks.
weave driver
- This runs in what Docker calls "global scope", which requires an external cluster store
- Supports multiple networks that must be created using
docker network create --driver weave ... - Used with Docker's cluster-store-based IPAM
There's no specific documentation from Docker on using a cluster store, but the first part of Getting Started with Docker Multi-host Networking is a good place to start.
Note: In the case of multiple networks using the
weavedriver, all containers are on the same virtual network but Docker allocates their addresses on different subnets so they cannot talk to each other directly.
See Also