This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 14.000000000000002%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECO%3C/text%3E%3C/svg%3E)
The Docker service cannot be found for the Cloud Shell CLI, the node cannot be logged in remotely, and an error is reported when logging in to the bastion host.
Hi Chen, Owen
you need to ssh into the AKS worker nodes and check the images ?
can you clarify what you need to do ?
Also you can ssh into the node by using this , kubectl debug
https://learn.microsoft.com/en-us/azure/aks/node-access#ssh-using-kubectl-debug
And you can run crictl inside the worker node to view the images
crictl images
We want to take out the image and put it in the image repository and deploy a test environment, but AKS can't find the image when it logs in to Cloud Shell.
If you use the public IP address of the AKS node, you cannot log in to the SSH remotely.If you use the kubectl bebug command, you will see that there is no crictl command.
you want to push custom image deployed on AKS cluster node to Repo?
but you dont have copy of this image on your dev environment or docker file to build it ?
can you send screenshot of the crictl from inside the AKS node ?
use kubectl debug
and then crictl images
I'm sorry, the mirror has been found. Thank you very much
We use kubectl debug node/aks-agentpool-21107632-vmss000007 -it --image=mcr.microsoft.com/cbl-mariner/busybox:2.0 to log in to the node but we don't use this command；
sorry i forgot to mention that you need to switch to node context
chroot /host
please run it after you run kubectl debug and then you can run crictl images
You can interact with the node session by running chroot /host from the privileged container.
That's okay, but why did I use this command when I couldn't find the image in my yaml file on any node
Why does the push image look like this?