<p>I created a new kubernetes cluster (GKE) and installed an application using helm.</p>
<p>I was able to locate the gke-node on which my pod was deployed using the command,
<code>kubectl get pod -n namespace -o wide</code></p>
<p>Post that i logged on to the kubernetes-node, however on this node i am unable to view the docker images. This is the case on v1.21.4-gke.2300</p>
<p>In the older-version v1.19.13-gke.1200, i was able to observe the docker-images on nodes when they were pulled from repository</p>
<p>I can view the list of docker-images on v1.21.4-gke.2300 with the command
<code>kubectl get pods -n geo-test -o jsonpath=&quot;{.items[*].spec.containers[*].image}&quot; | tr -s '[[:space:]]' '\n' |  sort |  uniq -c</code></p>
<p>But i would like to know where in the cluster are these images getting stored and why i am not able to observe them in the node like i did in the older version</p>
<p>My reason for asking is, because in version v1.19.13-gke.1200, i was able to perform minor changes in the docker-image, build a custom-image and use that for installation instead of storing the images in the gcr and pulling it from there
Any suggestion on how to go about it in the new</p>
<p><a href="https://i.stack.imgur.com/bZhmj.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/bZhmj.png" alt="v1.19.13-gke.1200" /></a></p>

<p>Starting with GKE node version 1.19, the default node image for Linux nodes is the Container-Optimized OS with containerd (cos_containerd) variant instead of the Container-Optimized OS with Docker (cos) variant.</p>
<p>Now instead of <code>docker</code> commands you can use <code>crictl</code>. Refer to the <a href="https://kubernetes.io/docs/tasks/debug-application-cluster/crictl/" rel="noreferrer">crictl user guide</a> for the complete set of supported features and usage information.</p>
<p>Specifically, you can run <code>crictl images</code> to list the images, available on the node.</p>
