kube-multus status Init:CreateContainerError in microk8s

[panpur]

Hello,

I tried to deploy thin plugin:

cat ./deployments/multus-daemonset.yml | sudo microk8s.kubectl apply -f -
customresourcedefinition.apiextensions.k8s.io/network-attachment-definitions.k8s.cni.cncf.io created
clusterrole.rbac.authorization.k8s.io/multus created
clusterrolebinding.rbac.authorization.k8s.io/multus created
serviceaccount/multus created
configmap/multus-cni-config created
daemonset.apps/kube-multus-ds created

But the kube-multus status is Init:CreateContainerError
Here's the describe output:

Name:             kube-multus-ds-m76bd
Namespace:        kube-system
Priority:         0
Service Account:  multus
Node:             vmcwpu19/172.30.44.168
Start Time:       Wed, 21 Dec 2022 14:02:34 +0530
Labels:           app=multus
                  controller-revision-hash=5cd8dd6749
                  name=multus
                  pod-template-generation=1
                  tier=node
Annotations:      <none>
Status:           Pending
IP:               172.30.44.168
IPs:
  IP:           172.30.44.168
Controlled By:  DaemonSet/kube-multus-ds
Init Containers:
  install-multus-binary:
    Container ID:
    Image:         ghcr.io/k8snetworkplumbingwg/multus-cni:stable
    Image ID:
    Port:          <none>
    Host Port:     <none>
    Command:
      cp
      /usr/src/multus-cni/bin/multus
      /host/opt/cni/bin/multus
    State:          Waiting
      Reason:       CreateContainerError
    Ready:          False
    Restart Count:  0
    Requests:
      cpu:        10m
      memory:     15Mi
    Environment:  <none>
    Mounts:
      /host/opt/cni/bin from cnibin (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-8kcqf (ro)
Containers:
  kube-multus:
    Container ID:
    Image:         ghcr.io/k8snetworkplumbingwg/multus-cni:stable
    Image ID:
    Port:          <none>
    Host Port:     <none>
    Command:
      /entrypoint.sh
    Args:
      --multus-conf-file=auto
      --cni-version=0.3.1
    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Limits:
      cpu:     100m
      memory:  50Mi
    Requests:
      cpu:        100m
      memory:     50Mi
    Environment:  <none>
    Mounts:
      /host/etc/cni/net.d from cni (rw)
      /host/opt/cni/bin from cnibin (rw)
      /tmp/multus-conf from multus-cfg (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-8kcqf (ro)
Conditions:
  Type              Status
  Initialized       False
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  cni:
    Type:          HostPath (bare host directory volume)
    Path:          /etc/cni/net.d
    HostPathType:
  cnibin:
    Type:          HostPath (bare host directory volume)
    Path:          /opt/cni/bin
    HostPathType:
  multus-cfg:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      multus-cni-config
    Optional:  false
  kube-api-access-8kcqf:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 :NoSchedule op=Exists
                             :NoExecute op=Exists
                             node.kubernetes.io/disk-pressure:NoSchedule op=Exists
                             node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                             node.kubernetes.io/network-unavailable:NoSchedule op=Exists
                             node.kubernetes.io/not-ready:NoExecute op=Exists
                             node.kubernetes.io/pid-pressure:NoSchedule op=Exists
                             node.kubernetes.io/unreachable:NoExecute op=Exists
                             node.kubernetes.io/unschedulable:NoSchedule op=Exists
Events:
  Type    Reason  Age                 From     Message
  ----    ------  ----                ----     -------
  Normal  Pulled  99s (x49 over 11m)  kubelet  Container image "ghcr.io/k8snetworkplumbingwg/multus-cni:stable" already present on machine

I've also tried with microk8s enable multus, but it's showing neverending Waiting for multus daemonset to start
I'm testing on WSL2 Ubuntu 20.
Any idea on what causing this?

Thanks