Apr 25 17:11:34 k8s_n1 kubelet: I0425 17:11:34.860041    2476 kuberuntime_manager.go:742] checking backoff for container "wordpress" in pod "wordpress-1595585052-n89d8_default(f63ddbae-2995-11e7-a7d0-5254000d6f84)"

Apr 25 17:11:34 k8s_n1 kubelet: I0425 17:11:34.860221    2476 kuberuntime_manager.go:752] Back-off 20s restarting failed container=wordpress pod=wordpress-1595585052-n89d8_default(f63ddbae-2995-11e7-a7d0-5254000d6f84)

Apr 25 17:11:34 k8s_n1 kubelet: E0425 17:11:34.860343    2476 pod_workers.go:182] Error syncing pod f63ddbae-2995-11e7-a7d0-5254000d6f84 ("wordpress-1595585052-n89d8_default(f63ddbae-2995-11e7-a7d0-5254000d6f84)"), skipping: failed to "StartContainer" for "wordpress" with CrashLoopBackOff: "Back-off 20s restarting failed container=wordpress pod=wordpress-1595585052-n89d8_default(f63ddbae-2995-11e7-a7d0-5254000d6f84)"

Apr 25 17:11:35 k8s_n1 kubelet: I0425 17:11:35.513133    2476 operation_generator.go:597] MountVolume.SetUp succeeded for volume "kubernetes.io/secret/3a44f3e6-256b-11e7-8373-5254000d6f84-default-token-73np4" (spec.Name: "default-token-73np4") pod "3a44f3e6-256b-11e7-8373-5254000d6f84" (UID: "3a44f3e6-256b-11e7-8373-5254000d6f84").

Apr 25 17:11:35 k8s_n1 kubelet: W0425 17:11:35.572486    2476 docker_sandbox.go:263] Couldn‘t find network status for default/wordpress-1595585052-n89d8 through plugin: invalid network status for

Apr 25 17:11:42 k8s_n1 kubelet: I0425 17:11:42.703337    2476 helpers.go:101] Unable to get network stats from pid 25234: couldn‘t read network stats: failure opening /proc/25234/net/dev: open /proc/25234/net/dev: no such file or directory

Apr 25 17:11:47 k8s_n1 kubelet: I0425 17:11:47.208676    2476 helpers.go:101] Unable to get network stats from pid 24895: couldn‘t read network stats: failure opening /proc/24895/net/dev: open /proc/24895/net/dev: no such file or directory

Apr 25 17:11:48 k8s_n1 kubelet: I0425 17:11:48.457148    2476 operation_generator.go:597] MountVolume.SetUp succeeded for volume "kubernetes.io/secret/f63ddbae-2995-11e7-a7d0-5254000d6f84-default-token-h49ds" (spec.Name: "default-token-h49ds") pod "f63ddbae-2995-11e7-a7d0-5254000d6f84" (UID: "f63ddbae-2995-11e7-a7d0-5254000d6f84").

Apr 25 17:11:48 k8s_n1 kubelet: I0425 17:11:48.736002    2476 kuberuntime_manager.go:458] Container {Name:wordpress Image:wordpress:4.7.3-apache Command:[] Args:[] WorkingDir: Ports:[{Name:wordpress HostPort:0 ContainerPort:80 Protocol:TCP HostIP:}] EnvFrom:[] Env:[{Name:WORDPRESS_DB_HOST Value:wordpress-mysql ValueFrom:nil} {Name:WORDPRESS_DB_PASSWORD Value: ValueFrom:&EnvVarSource{FieldRef:nil,ResourceFieldRef:nil,ConfigMapKeyRef:nil,SecretKeyRef:&SecretKeySelector{LocalObjectReference:LocalObjectReference{Name:mysql-pass,},Key:password.txt,Optional:nil,},}}] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:wordpress-persistent-storage ReadOnly:false MountPath:/var/www/html SubPath:} {Name:default-token-h49ds ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath:}] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it.

Apr 25 17:11:48 k8s_n1 kubelet: I0425 17:11:48.736342    2476 kuberuntime_manager.go:742] checking backoff for container "wordpress" in pod "wordpress-1595585052-n89d8_default(f63ddbae-2995-11e7-a7d0-5254000d6f84)"

Apr 25 17:11:48 k8s_n1 kubelet: I0425 17:11:48.736586    2476 kuberuntime_manager.go:752] Back-off 20s restarting failed container=wordpress pod=wordpress-1595585052-n89d8_default(f63ddbae-2995-11e7-a7d0-5254000d6f84)

Apr 25 17:11:48 k8s_n1 kubelet: E0425 17:11:48.736660    2476 pod_workers.go:182] Error syncing pod f63ddbae-2995-11e7-a7d0-5254000d6f84 ("wordpress-1595585052-n89d8_default(f63ddbae-2995-11e7-a7d0-5254000d6f84)"), skipping: failed to "StartContainer" for "wordpress" with CrashLoopBackOff: "Back-off 20s restarting failed container=wordpress pod=wordpress-1595585052-n89d8_default(f63ddbae-2995-11e7-a7d0-5254000d6f84)"

Apr 25 17:11:50 k8s_n1 kubelet: I0425 17:11:50.465307    2476 operation_generator.go:597] MountVolume.SetUp succeeded for volume "kubernetes.io/secret/3ab8dbab-256b-11e7-8373-5254000d6f84-elasticsearch-token-szhsl" (spec.Name: "elasticsearch-token-szhsl") pod "3ab8dbab-256b-11e7-8373-5254000d6f84" (UID: "3ab8dbab-256b-11e7-8373-5254000d6f84").

Apr 25 17:11:56 k8s_n1 kubelet: E0425 17:11:56.687817    2476 fsHandler.go:121] failed to collect filesystem stats - rootDiskErr: <nil>, rootInodeErr: <nil>, extraDiskErr: du command failed on /var/lib/docker/containers/f1eb964f079a7e59503c013434c9503947043b83e12b817a062c3c10ae623c4d with output stdout: , stderr: du: cannot access ‘/var/lib/docker/containers/f1eb964f079a7e59503c013434c9503947043b83e12b817a062c3c10ae623c4d’: No such file or directory

Apr 25 17:11:56 k8s_n1 kubelet: - exit status 1

本文出自 “Docker_in_Cloud” 博客，请务必保留此出处http://docker.blog.51cto.com/7887690/1919316

k8s wordpress pod启动不了