Bryan Boreham

Current behaviour of `prog/weave-kube/launch.sh` is to try `/opt/cni/bin` then `/home/kubernetes/bin` which is where ContainerOS puts it. We could inspect the kubelet args. Or just add a third...

I think it's ok to add a third option, and to add an environment variable. Note we are talking about the bin dir not the conf dir. What is also...

@rajch The problem was that Kubelet is looking somewhere else? Which kubelet, and where is it looking?

> ... Please don't do this; we ask for the logs because there is information there that helps to speed troubleshooting. Please include the whole log, at least the first...

Something unusual about your kernel? Could you provide version details please.

Thanks for the update. I believe Weave Net uses the dummy device as a way to make some network settings. Usually I would ask that you open a new issue...

If someone wants to make a PR to give Weave Net an alternate way to achieve what it needs, that would be great.

This is broadly the same as #59

#86 could be used to add a rate-limiter from the outside. Or a circuit-breaker, which is perhaps an even better idea.

Update: I added a circuit-breaker using the code from #86, and the symptoms went away. I would like to see #86 merged.