Answers: <p>I had this happen to me when my flannel and cni0 inet addresses were out of sync. Bringing down the cni0 bridge made it resync for me:</p>
  <pre><code>ifconfig cni0 down
  brctl delbr cni0
  </code></pre>
  <p>Or if that doesn't work:</p>
  <pre><code>sudo ip link delete cni0 type bridge
  </code></pre>
  <p>Hope that helps.</p>
  
Answers: CC BY-SA 4.0
Answers: 2022-09-24T10:44:45.597Z
Answers: actually had this again on another cluster a few weeks ago. will try soon
Answers: Serve Laurijssen
Answers: CC BY-SA 4.0
Answers: 2023-10-05T19:56:20.460Z
Answers: Second option worked for me, thanks!
Answers: englishPete
Answers: CC BY-SA 4.0
Answers: 2022-09-21T22:14:53.267Z
Answers: 2022-09-21T22:16:01.660Z
Answers: 2022-09-21T22:16:01.660Z
Answers: user37018
Body: <p>I've got a k8s (on-premise) cluster with 1 master and 3 workers, all ubuntu, latest LTS version.</p>
  <p>2 workers are running fine, but pods getting scheduled to one stay in the ContainerCreating state with the error.</p>
  <blockquote>
  <p>Failed to create pod sandbox: rpc error: code = Unknown desc = failed
  to set up sandbox container &quot;1234&quot; network for pod
  &quot;clean-updater-hxknv&quot;: networkPlugin cni failed to set up pod
  &quot;clean-updater-hxknv_default&quot; network: failed to set bridge addr:
  &quot;cni0&quot; already has an IP address different from 10.244.6.1/24</p>
  </blockquote>
  <p>cni0 has an ip of:</p>
  <p>cni0: &lt;BROADCAST,MULTICAST,UP&gt; mtu 1500 qdisc noqueue state UP group default qlen 1000
  inet 10.244.3.1/24 brd 10.244.3.255 scope global cni0</p>
  <p>I've tried kubeadm reset and join again on the node but it didnt help. How to fix this error?</p>
  
Tags: <docker><kubernetes>
Title: cni0 already has an ip address
UserDisplayName: Serve Laurijssen
ThreadText: # cni0 already has an ip address
  
  (Asked by: username_0 on 2021-10-27)
  
  I've got a k8s (on-premise) cluster with 1 master and 3 workers, all ubuntu, latest LTS version.
  
  2 workers are running fine, but pods getting scheduled to one stay in the ContainerCreating state with the error.
  
  > Failed to create pod sandbox: rpc error: code = Unknown desc = failed
  > to set up sandbox container "1234" network for pod
  > "clean-updater-hxknv": networkPlugin cni failed to set up pod
  > "clean-updater-hxknv\_default" network: failed to set bridge addr:
  > "cni0" already has an IP address different from 10.244.6.1/24
  
  cni0 has an ip of:
  
  cni0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
  inet 10.244.3.1/24 brd 10.244.3.255 scope global cni0
  
  I've tried kubeadm reset and join again on the node but it didnt help. How to fix this error?
  
  **Tags:** docker, kubernetes
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2022-09-21. Score: 3 | Accepted answer
  
  I had this happen to me when my flannel and cni0 inet addresses were out of sync. Bringing down the cni0 bridge made it resync for me:
  
  ```
  ifconfig cni0 down
  brctl delbr cni0
  
  ```
  
  Or if that doesn't work:
  
  ```
  sudo ip link delete cni0 type bridge
  
  ```
  
  Hope that helps.
  
  > **Comments:**
  > **username_0**: actually had this again on another cluster a few weeks ago. will try soon  
  > **username_2**: Second option worked for me, thanks!  
  
  ---
  
  