-
Notifications
You must be signed in to change notification settings - Fork 673
FATA: creating dummy interface: operation not supported #3776
Comments
@Roarain As part of weave-net pod startup steps, a dummy interface is created and deleted. For some reason on your setup it is failing to get created. Can you please try |
Just encountered this. Running the command above gives me following
|
Something unusual about your kernel? Could you provide version details please. |
@bboreham Sure.
Also, weave reports some additional things in logs:
Servers are Scaleway's cloud instances, currently I am trying to make it work with k3s. Potentially it might be related (I guess) to the openswitch warning above, I'll try to install it and see if anything changes. |
I've potentially found the issue. Looks like kvm kernel (https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1833375) doesn't have dummy module
I'll try to find out if it's possible to add this module (not sure if it's possible with kvm kernels). Otherwise is the dummy interface interface essential for weave functionality? |
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 to avoid confusion with the original one, which has slightly different symptoms. But they never followed up. |
Yep, just ran into this with the kvm kernel. Switched to the generic kernel and it works fine there. |
If someone wants to make a PR to give Weave Net an alternate way to achieve what it needs, that would be great. |
I had the same error on my Raspberry Pi 5 with Ubuntu 23.10 installed. |
Install WeaveNet as pod network add-on according to doc https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#pod-network
but got this error and result to coreDNS pending
OS info
interface info, xgbe1 as the k8s cluster interface
Error
pod info
Does any One help me ?
The text was updated successfully, but these errors were encountered: