<p>I have a one node cluster (managed by Rancher) which wasn't setup by me so I dont know the details.</p>
<p><code>kubectl get nodes</code> returns one node named <code>node-1</code>; <br>
<code>kubectl get pods -o wide</code> shows that every (~40) pod running on that <code>node-1</code> (of course).</p>
<p>But when I ssh into <code>node-1</code> as root the <code>docker ps</code> command shows only <code>rancher/rancher:v2.6.3</code> as running container.</p>
<p>So what hides Rancher from us? Where can I access the docker context of the running pods?</p>

beatrice
<p>The <code>docker ps</code> command most likely won't return what you expected because Kubernetes dropped Docker as a container runtime about a year ago. This doesn't mean container images built by Docker won't run in Kubernetes, it just means that some of Docker's underlying functionalities are not included with Kubernetes.</p>
<p>It seems that Rancher itself does run as a Docker container, however the pods themselves do not. If you wanted to interact with the pods from within the node, you can look into <a href="https://github.com/containerd/nerdctl" rel="nofollow noreferrer">nerdctl</a> or <a href="https://github.com/projectatomic/containerd/blob/master/docs/cli.md" rel="nofollow noreferrer">ctr</a> (assuming your cluster's container runtime is <a href="https://github.com/containerd/containerd" rel="nofollow noreferrer">containerd</a>).</p>
