使用kubernetes创建容器一直处于ContainerCreating状态的原因查找与解决

[root@k8s-master demo]# kubectl get pod

NAME      READY     STATUS              RESTARTS   AGE

busybox   0/1       ContainerCreating   0          12m


[root@k8s-master demo]# kubectl describe pod busybox

Name:           busybox

Namespace:      default

Node:           k8s-node-1/10.0.0.12

Start Time:     Thu, 07 Jun 2018 09:53:48 +0800

Labels:         <none>

Status:         Pending

IP:

Controllers:    <none>

Containers:

  busybox:

    Container ID:

    Image:       10.0.0.10:5000/busybox

    Image ID:

    Port:

    Command:

      sleep

      3600

    State:       Waiting

      Reason:    ContainerCreating

    Ready:       False

    Restart Count:    0

    Volume Mounts:    <none>

    Environment Variables:  <none>

Conditions:

  Type        Status

  Initialized   True 

  Ready       False 

  PodScheduled  True 

No volumes.

QoS Class:      BestEffort

Tolerations:    <none>

Events:

FirstSeen  LastSeen  Count  From           SubObjectPath   Type      Reason    Message

---------  --------  -----  ----           -------------   --------   ------      -------

 15m     15m       1   {default-scheduler }            Normal    Scheduled    Successfully assigned busybox to k8s-node-1

 15m     22s      64   {kubelet k8s-node-1}            Warning    FailedSync   Error syncing pod, skipping: failed to "StartContainer" for "POD" with ImagePullBackOff: "Back-off pulling image \"registry.access.redhat.com/rhel7/pod-infrastructure:latest\""

 15m    11s       8    {kubelet k8s-node-1}            Warning FailedSync      Error syncing pod, skipping: failed to "StartContainer" for "POD" with ErrImagePull: "image pull failed for registry.access.redhat.com/rhel7/pod-infrastructure:latest, this may be because there are no credentials on this request.  details: (open /etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt: no such file or directory)"








猜你喜欢

转载自blog.51cto.com/sf1314/2125850
今日推荐