Difference between revisions of "Crictl exec"
Jump to navigation
Jump to search
| (One intermediate revision by one other user not shown) | |||
| Line 2: | Line 2: | ||
crictl exec -i -t 1f73f2d81bf98 ls | crictl exec -i -t 1f73f2d81bf98 ls | ||
| + | |||
| + | == Related == | ||
| + | * <code>[[docker exec]]</code> | ||
== See also == | == See also == | ||
Latest revision as of 08:32, 28 December 2022
crictl exec -i -t 1f73f2d81bf98 ls
Related[edit]
See also[edit]
crictl [ logs | ps | pods | exec | config | images ], /etc/crictl.yaml, crictl --help, Kubelet Container Runtime Interface (CRI)- K8s troubleshooting:
kubectl logs, kubectl top, kubectl get events -A, kubectl describe pod, Liveness, Readiness,Kubernetes events, Pulling image, OOMKilled, ProbeWarning, Reason,FailedScheduling,errImagePull, ImagePullBackOff, Kubelet conditions:MemoryPressure, DiskPressure, KubeletHasSufficientPID, KubeletReady, kubectl [ debug | attach | exec ] kubectl cluster-info dump, SimKube, KWOK
Advertising:
