kinvolk/kube-spawn

Fails to set up bridge with CNI

Closed this issue · 0 comments

I think this is because syscall.ForkExec is used in pkg/bootstrap/bridge.go instead of the usual os/exec library. The difference is that syscall.ForkExec is basically fork + execve, and execve does not check the PATH environment variable.

What was the reason for using syscall.ForkExec?

Here is the output:

[root@localhost ([k8s], [go-1.9, kinvolk]) kinvolk]# kube-spawn create --nodes 1 --image coreos
creating cluster environment "default"
spawning kubernetes version "v1.7.5"
downloading 10-kubeadm.conf
downloading kubectl
downloading kubeadm
downloading kubelet
downloading kubelet.service
downloading socat
ensuring environment
error checking CNI bridge: no such file or directory
[root@localhost ([k8s], [go-1.9, kinvolk]) kinvolk]# which cni-noop
/home/kv/projects/kinvolk/GOPATH/bin/cni-noop