Difference between revisions of "Crictl logs"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
|||
| Line 6: | Line 6: | ||
I0913 12:53:03.096620 1 server_others.go:212] Using [[iptables Proxier]]. | I0913 12:53:03.096620 1 server_others.go:212] Using [[iptables Proxier]]. | ||
... | ... | ||
| + | |||
| + | WARN[0000] runtime connect using default endpoints: [unix:///var/run/dockershim.sock unix:///run/containerd/containerd.sock unix:///run/crio/crio.sock unix:///var/run/cri-dockerd.sock]. As the default settings are now deprecated, you should set the endpoint instead. | ||
| + | FATA[0000] [[ID cannot be empty]] | ||
== Related == | == Related == | ||
Latest revision as of 21:21, 12 March 2023
crictl logs 27b6a18c0f89c ... I0913 12:53:03.096620 1 server_others.go:212] Using iptables Proxier. ...
WARN[0000] runtime connect using default endpoints: [unix:///var/run/dockershim.sock unix:///run/containerd/containerd.sock unix:///run/crio/crio.sock unix:///var/run/cri-dockerd.sock]. As the default settings are now deprecated, you should set the endpoint instead. FATA[0000] ID cannot be empty
Related[edit]
kubectl logs ktail crictl ps
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:
