<p>I am trying to set up a kubernetes cluster and running this command on my worker node
<code>kubeadm join server:port --token xxx  --discovery-token-ca-cert-hash sha256:xxxx</code>
and the error i have is</p>
<pre><code>Found multiple CRI endpoints on the host. Please define which one do you wish to use by setting the 'criSocket' field in the kubeadm configuration file: unix:///var/run/containerd/containerd.sock, unix:///var/run/cri-dockerd.sock
</code></pre>
<p>I am not sure which container runtime to use here, so i modified the command as
<code>kubeadm join server:port --token xxx  --discovery-token-ca-cert-hash sha256:xxxx --cri-socket /var/run/crio/crio.sock</code>
but the error is</p>
<pre><code>[ERROR CRI]: container runtime is not running: output: I0617 21:55:27.908044 1877581 util_unix.go:103] &quot;Using this endpoint is deprecated, please consider using full URL format&quot; endpoint=&quot;/var/run/crio/crio.sock&quot; URL=&quot;unix:///var/run/crio/crio.sock&quot;
E0617 21:55:27.908867 1877581 remote_runtime.go:616] &quot;Status from runtime service failed&quot; err=&quot;rpc error: code = Unavailable desc = connection error: desc = \&quot;transport: Error while dialing dial unix /var/run/crio/crio.sock: connect: no such file or directory\&quot;&quot;
time=&quot;2023-06-17T21:55:27+05:30&quot; level=fatal msg=&quot;getting status of runtime: rpc error: code = Unavailable desc = connection error: desc = \&quot;transport: Error while dialing dial unix /var/run/crio/crio.sock: connect: no such file or directory\&quot;&quot;
, error: exit status 1
</code></pre>
<p>Can someone suggest the correct approach here</p>

noob_coder
<p><code>cri-socket</code> is which container runtime in the host you want to use.</p>
<ul>
<li>If there is only one of <code>cri-o</code>`cri-dockerd<code>\</code>containerd`, it will auto detect and choose it for you.</li>
<li>In your case, there are two: <code>cri-dockerd</code> and <code>containerd</code>. So kubeadm cannot decide which to use. You should make a decision.</li>
<li>If you don't want either cri-docker for docker or containerd.sock for containerd, you should install <a href="https://github.com/cri-o/cri-o" rel="nofollow noreferrer">cri-o</a> before using it.</li>
</ul>
