docker-plugin
docker-plugin copied to clipboard
weaveworks-experiments
Deprecated, part of Weave Net now
`docker network create --driver=weave --gateway=...` provokes no complaint, neither on the command line nor in a log, even though this gateway concept is not really supported by this plugin.
I'm not sure in what circumstances we want to provide a default gateway; perhaps always, since we can usually assume we'll be the only interface. But is it correct to...
Weave's IPAM supports only one subnet at present, which means (assuming IPAM is the only kind of co-ordination) that the weave plugin can have only one network. So this will...
I think the plugin will get told the port mapping; so it's possible we could support port mapping, and remove the need for adding a container to the bridge network.
We should set the veth MAC address to be the same as that we report back to libnetwork.
At present the driver is not told either of the containerID or the hostname, so it is more or less impossible in remote driver terms to register containers with weaveDNS....
Harder than it sounds. There are two requirements: 1. The plugin has to be able to put `nameserver x.x.x.x` in the container's `/etc/resolv.conf` 2. The container has to be able...