pod in ContainerCreating - error adding container to network "x": Link not found

[ritokispingvin]

Hi,

my pod stays in ContainerCreating status.

Kubectl describe pod UPF:

I've tried to set this up on both minikube and kubeadm, both with flannel and calico CNIs but all my trials resulted in same issue.

My current network config:

NetworkAttachmentDefinition is following. Only n6 network uses eth1 so I'm listing only that. All other pods are using eth0 which is working fine as those pods are running.

If I set n6 network to use eth0 instead of eth1 then the UPF pod is created successfully, but I need to attach it to eth1 for my project. So I think it is some issue when using a secondary interface.

Thank you and best regards, Tamas

[dougbtv]

Looks like the delegated CNI plugin is reporting link not found -- which seems like it can't find the interface on the host side. This looks like a platform problem from here that the corresponding NIC name isn't found. May be worth double checking that it's there, and/or looking into it from the virtualization platform angle

[camilla-m]

Hi! I'm having precisely the same problem, but I'm very new at network interfaces at k8s and don't know exactly how to debug it and solve it. When I try to search for the problem on the internet I don't receive information accurate enough to go deeper into it. Can anyone give a tip?

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[jose-galvao]

I had the same problem. How did you solve it?

[ritokispingvin]

Hi, unfortunately I haven't been able to solve the issue back then. Right now I think setting the adapter 1 to NAT instead of host only might worth a shot, but I can't test it myself anymore. BRs, Tamas

[jose-galvao]

Thanks