The SR-IOV additional network ipam CNI plug-in with type 'dhcp' fails with error "dial unix /run/cni/dhcp.sock: connect: no such file or directory"

Solution Verified - Updated -


  • When configuring the SR-IOV additional network ipam CNI plug-in with type dhcp, it fails with error as shown below.
Warning  FailedCreatePodSandBox  <invalid> (x30 over <invalid>)  kubelet,  (combined from similar events): Failed create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_sriov-pod-test_openshift-sriov-network-operator_53e17d4c-1476-4f91-a8b5-175e3188886d_0(71ae0946ad7dc4455e0e312b4ff890dd9bbcd231b8e3070c298197dd4be1650a): Multus: [openshift-sriov-network-operator/sriov-pod-test]: error adding container to network "sriov-net": delegateAdd: error invoking DelegateAdd - "sriov": error in getting result from AddNetwork: failed to set up IPAM plugin type "dhcp" from the device "ens1f0": error dialing DHCP daemon: dial unix /run/cni/dhcp.sock: connect: no such file or directory


  • OpenShift Container Platform 4.3
  • SR-IOV additional network Configuration.
  • ipam CNI plug-in with type 'DHCP'

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content