Difference between revisions of "Kubectl logs my-pod -c my-container"
Jump to navigation
Jump to search
| (3 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
[[standard_init_linux.go:228: exec user process caused: exec format error]] | [[standard_init_linux.go:228: exec user process caused: exec format error]] | ||
| − | kubectl logs -n kube-system aws-node-w75dq -c aws-vpc-cni-init | + | [[kubectl logs -n kube-system]] aws-node-w75dq -c [[aws-vpc-cni-init]] |
| − | Error from server (BadRequest): container "aws-vpc-cni-init" in pod "aws-node-w75dq" is waiting to start: PodInitializing | + | Error from server ([[BadRequest]]): [[container]] "aws-vpc-cni-init" in pod "[[aws-node-w75dq]]" is waiting to start: [[PodInitializing]] |
Latest revision as of 12:44, 22 February 2024
kubectl logs my-pod -c my-container standard_init_linux.go:228: exec user process caused: exec format error
kubectl logs -n kube-system aws-node-w75dq -c aws-vpc-cni-init Error from server (BadRequest): container "aws-vpc-cni-init" in pod "aws-node-w75dq" is waiting to start: PodInitializing
See also[edit]
kubectl logs, ktail, stern, --previous, -c- 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 - Kubectl information commands:
cluster-info|view|pods|nodes|services|version|describe | logs
Advertising:
