66837d6f3b
Running ginkgo tests in parallel causes problems with dhcp_test.go. BeforeEach() is run once for each spec before any actual dhcp test starts. This results in setting up two dhcp4servers that run concurrently. Both try to Listen and use unix socketPath file /run/cni/dhcp.sock at the same time. AfterEach() for one test runs when test completes, deleting /run/cni/dhcp.sock. But other test still needs the file resulting in test failing. Often, the next dhcp test hasn't started yet. When test does start it waits 15 seconds for dhcp4server to create /run/cni/dhcp.sock (which has just been deleted) so test fails. Other times dhcp tests fail because /run/cni/dhcp.sock is deleted while still being used.
plugins
Some CNI network plugins, maintained by the containernetworking team. For more information, see the individual READMEs.
Read CONTRIBUTING for build and test instructions.
Plugins supplied:
Main: interface-creating
bridge: Creates a bridge, adds the host and the container to it.ipvlan: Adds an ipvlan interface in the container.loopback: Set the state of loopback interface to up.macvlan: Creates a new MAC address, forwards all traffic to that to the container.ptp: Creates a veth pair.vlan: Allocates a vlan device.
Windows: windows specific
win-bridge: Creates a bridge, adds the host and the container to it.win-overlay: Creates an overlay interface to the container.
IPAM: IP address allocation
dhcp: Runs a daemon on the host to make DHCP requests on behalf of the containerhost-local: maintains a local database of allocated IPs
Meta: other plugins
flannel: generates an interface corresponding to a flannel config filetuning: Tweaks sysctl parameters of an existing interfaceportmap: An iptables-based portmapping plugin. Maps ports from the host's address space to the container.
Sample
The sample plugin provides an example for building your own plugin.