I have this doubt: because instead of going to the worker node and restarting the container from crictl you did not do an exec -it of the container and from there there is a shutdown -r now
hi, Kubernetes does not directly use Docker for container management on its nodes So, when you run docker ps on a Kubernetes node, you are interacting with Docker's native runtime, which is separate from the container runtime used by Kubernetes. This is why you don't see Kubernetes containers listed.
excellent
I have this doubt: because instead of going to the worker node and restarting the container from crictl you did not do an exec -it of the container and from there there is a shutdown -r now
hi, in the question they may ask to restart the container to make event logs, that is why we are restarting the container.
hi, why CRICTL using instead docker ps for listing containers?
hi, Kubernetes does not directly use Docker for container management on its nodes
So, when you run docker ps on a Kubernetes node, you are interacting with Docker's native runtime, which is separate from the container runtime used by Kubernetes. This is why you don't see Kubernetes containers listed.