Bryan Boreham
Bryan Boreham
Looking at the upstream issue https://github.com/istio/cni/issues/22 I think your problem is with the way various network implementations are distributed as Kubernetes DaemonSets which write a single config file out to...
A container may be attached to multiple networks. The interface name was added in #551, because a container can be added multiple times to the same network, but we don't...
How about: "`name` can be used to identify different configurations on the host, and may be used by plugins for logging, or for any other purpose. Whether names are unique...
I believe this is covered [in the spec](https://github.com/containernetworking/cni/blob/master/SPEC.md#network-configuration-list-error-handling): > If an ADD action fails, when the runtime decides to handle the failure it should execute the DEL action (in reverse...
Do you mean crash as in "panic", or some more general concept of "really bad error where we can't recover enough to call DEL, but haven't actually killed the process"...
CNI is an interface: it allows any kind of network to have a “plugin” to connect things up for a “runtime”. Suggest viewing one of the “intro to CNI” videos,...
ping @whustone - waiting on you to add more information
Thanks! The SPEC is not supposed to document libcni; it is an independent specification. We could have more explicit documentation for libcni and/or pointers in the README.
It seems to me you ought to be able to use your own struct that embeds `Result`. I can see that this adds some work on the receiving end to...
Yes, PRs welcome.