<p>I am working on a centOS environment and I have configured kubectl using kubeadm to work with k8s and learn about it. I have configured it using containerd as I am working with k8s v1.26.2.</p>
<p>The problem is that I am not able to configure the coredns pod when executing kubeadm init as you can see here:</p>
<pre><code>[root@portov7 config_files]# kubectl get pods --all-namespaces
NAMESPACE      NAME                                              READY   STATUS                  RESTARTS   AGE
default        podtest                                           0/1     ContainerCreating       0          130m
kube-flannel   kube-flannel-ds-hqh9z                             0/1     Init:ImagePullBackOff   0          55m
kube-system    coredns-787d4945fb-2msm9                          0/1     ContainerCreating       0          154m
kube-system    coredns-787d4945fb-hms2c                          0/1     ContainerCreating       0          154m
kube-system    etcd-portov7.gre.hpecorp.net                      1/1     Running                 0          154m
kube-system    kube-apiserver-portov7.gre.hpecorp.net            1/1     Running                 0          154m
kube-system    kube-controller-manager-portov7.gre.hpecorp.net   1/1     Running                 0          154m
kube-system    kube-proxy-7r7nz                                  1/1     Running                 0          154m
kube-system    kube-scheduler-portov7.gre.hpecorp.net            1/1     Running                 0          154m
</code></pre>
<p>Seems that the problem is related to the flannel plugin that is not being found on the /opt/cni/bin directory. I have found that this plugin is not used anymore and I am thinking that maybe the problem is related to mu docker version(correct me if I am wrong please).</p>
<p>also, the problem here is that I have some docker containers running in parallel and I would like to migrate them to the latest docker version (currently I am using 1.13.1 version).</p>
<p>So I have two questions here:</p>
<ul>
<li>Is the flannel error generated by the docker version incompatibility somehow? I already created the 10-<strong>flannel.conflist</strong> flannel file but seems is not working.</li>
<li>If the docker version is the problem, the only way to migrate is by using the volumes to save the data and delete and recreate again the containers?</li>
</ul>
<p>Thank you in advance :)</p>

Luis Roset
<p>Already fixed it by performing the download and installation of the <a href="https://github.com/coreos/flannel/raw/master/Documentation/kube-flannel.yml" rel="nofollow noreferrer">https://github.com/coreos/flannel/raw/master/Documentation/kube-flannel.yml</a> file.</p>
<p>After the download I executed the command kubectl apply -f kube-flannel.yml and the flannel was configured and the coredns pods are running.</p>
<p>I had to add the <code>imagePullPolicy: Never</code> to the images after imported them to the CRI by using the <code>ctr</code> command.</p>
<pre><code>NAMESPACE      NAME                                              READY   STATUS    RESTARTS   AGE
kube-flannel   kube-flannel-ds-lx6cn                             1/1     Running   0          9s
kube-system    coredns-787d4945fb-5rjbv                          1/1     Running   0          27m
kube-system    coredns-787d4945fb-jqs5w                          1/1     Running   0          27m
kube-system    etcd-portov7.gre.hpecorp.net                      1/1     Running   2          27m
kube-system    kube-apiserver-portov7.gre.hpecorp.net            1/1     Running   2          27m
kube-system    kube-controller-manager-portov7.gre.hpecorp.net   1/1     Running   2          27m
kube-system    kube-proxy-mkrwd                                  1/1     Running   0          27m
kube-system    kube-scheduler-portov7.gre.hpecorp.net            1/1     Running   2          27m
</code></pre>
