# Kubernetes stuck in CrahLoopBackOff when I try to use multus

**URL:** <https://discuss.kubernetes.io/t/kubernetes-stuck-in-crahloopbackoff-when-i-try-to-use-multus/27753>\
**Category:** General Discussions\
**Created:** [April 4, 2024, 9:26am UTC](https://discuss.kubernetes.io/t/kubernetes-stuck-in-crahloopbackoff-when-i-try-to-use-multus/27753 "2024-04-04T09:26:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![paco2727](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/paco2727/32/14686_2.png) [@paco2727](https://discuss.kubernetes.io/u/paco2727)\
**Post date:** [April 4, 2024, 9:26am UTC](https://discuss.kubernetes.io/t/kubernetes-stuck-in-crahloopbackoff-when-i-try-to-use-multus/27753/1 "2024-04-04T09:26:24Z")

</div>

I have a master node and a worker node in two virtual machines, one virtual machine(Ubuntu) is master node and the other one(also Ubuntu) is the worker node.

After installing Multus CNI using the following command(I am following github tutorial):

```auto
kubectl apply -f https://raw.githubusercontent.com/k8snetworkplumbingwg/multus-cni/master/deployments/multus-daemonset-thick.yml

```

Kubernetes stuck in CrashLoopBackOff event and I don’t know how to solve it.

 ![multus](https://us1.discourse-cdn.com/flex016/uploads/kubernetes/original/2X/6/6a3fbb0f6a59ed27cf34648ef5edfed4a6ef6ab6.jpeg)

I’ve also installed Flannel before installing multus CNI from the github flannel repo and I haven’t had any problem.

Kubernetes version: 1.29.3  
Host OS: Ubuntu  
CNI and version: Multus(4.0 release)

---

<div class="post-metadata">

**Author:** ![HG1](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/hg1/32/10420_2.png) [@HG1](https://discuss.kubernetes.io/u/HG1)\
**Post date:** [May 17, 2024, 3:26pm UTC](https://discuss.kubernetes.io/t/kubernetes-stuck-in-crahloopbackoff-when-i-try-to-use-multus/27753/2 "2024-05-17T15:26:23Z")

</div>

Hi  
Did you have any luck?  
I am using Redhat and have the same issue but with Flannel.  
The problematic pod is on the node which you joined after the initial install I assume.  
I will give Ubuntu a try.  
Regards Hans