kind k8s sriov 1.14 provider throws permission denied after cluster up first time

[dhiller]

First time using kind k8s provider.

> export KUBEVIRT_PROVIDER=kind-k8s-sriov-1.14.2
> make cluster-up                                                                                                                                       
./cluster-up/up.sh                                                                                                                                      
DEBU[14:48:00] Running: /usr/bin/docker [docker ps -q -a --no-trunc --filter label=io.k8s.sigs.kind.cluster --format {{.Names}}\t{{.Label "io.k8s.sigs.k
ind.cluster"}}]                                                                                                                                         
...
++ _kubectl get nodes
++ grep sriov-worker
++ /home/dhiller/Projects/github.com/kubevirt/kubevirt/_ci-configs/kind-k8s-sriov-1.14.2/.kubectl --kubeconfig=/home/dhiller/Projects/github.com/kubevirt/kubevirt/_ci-configs/kind-k8s-sriov-1.14.2/.kubeconfig get nodes
+ [[ -z sriov-worker          Ready    <none>   40s   v1.14.2 ]]
+ SRIOV_NODE=sriov-worker
+ mkdir -p /var/run/netns/
mkdir: cannot create directory ‘/var/run/netns/’: Permission denied
make: *** [Makefile:101: cluster-up] Error 1

[dhiller]

Trying to create the directory with sudo didn't help, it then failed when creating a symlink later on:

+ mkdir -p /var/run/netns/                                                                                                                              
++ docker inspect -f '{{.State.Pid}}' sriov-worker                                                                                                      
+ export pid=1089553                                                        
+ pid=1089553                                                               
+ ln -sf /proc/1089553/ns/net /var/run/netns/sriov-worker                   
ln: failed to create symbolic link '/var/run/netns/sriov-worker': Permission denied
make: *** [Makefile:101: cluster-up] Error 1                                                                                                            

[dhiller]

After questioning around I got notice that I need to start it as root and have a SR-IOV enabled network card enabled. So I was just holding it wrong.

/close

[kubevirt-bot]

@dhiller: Closing this issue.

In response to this:

After questioning around I got notice that I need to start it as root and have a SR-IOV enabled network card enabled. So I was just holding it wrong.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.