<p>I have an weave network plugin.</p>
<p>inside my folder /etc/cni/net.d there is a 10-weave.conf</p>
<pre><code>{
&quot;name&quot;: &quot;weave&quot;,
&quot;type&quot;: &quot;weave-net&quot;,
&quot;hairpinMode&quot;: true
}
</code></pre>
<p>My weave pods are running and the dns pod is also running
But when I want to run a pod like a simple nginx which will pull an nginx image
The pod stuck at container creating, describe pod gives me the error, failed create pod sandbox.</p>
<p>When I run <code>journalctl -u kubelet</code> I get this error</p>
<blockquote>
<p>cni.go:171] Unable to update cni config: No networks found in /etc/cni/net.d</p>
</blockquote>
<p>is my network plugin not well configured?</p>
<p>I used this command to configure my weave network</p>
<pre><code>kubectl apply -f https://git.io/weave-kube-1.6
</code></pre>
<p>After this won't work I also tried this command</p>
<pre><code>kubectl apply -f “https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version | base64 | tr -d ‘\n’)”
</code></pre>
<p>I even tried flannel and that gives me the same error.
The system I am setting kubernetes on is a raspberry pi.
I am trying to build a raspberry pi cluster with 3 nodes and 1 master with kubernetes</p>
<p>Does anyone have ideas on this?</p>

achahbar
<p>Thank you all for responding to my question. I solved my problem now. For anyone who has come to my question in the future the solution was as followed.</p>

<p>I cloned my raspberry pi images because i wanted a basicConfig.img for when i needed to add a new node to my cluster of when one gets down.</p>

<p>Weave network (the plugin i used) got confused because on every node and master the os had the same machine-id. When i deleted the machine id and created a new one (and reboot the nodes) my error got fixed. The commands to do this was</p>

<p>sudo rm /etc/machine-id
sudo rm /var/lib/dbus/machine-id
sudo dbus-uuidgen --ensure=/etc/machine-id</p>

<p>Once again my patience was being tested. Because my kubernetes setup was normal and my raspberry pi os was normal. I founded this with the help of someone in the kubernetes community. This again shows us how important and great are IT community is. To the people of the future who will come to this question. I hope this solution will fix your error and will decrease the amount of time you will be searching after a stupid small thing.</p>
