Use Kubernetes to create a container that has been in the containercreating state for reasons of finding and resolving

[[email protected] demo]# kubectl get pod

NAME Ready STATUS Restarts

BusyBox 0/1 containercreating 0 12m

[Email protected] demo]# kubectl describe pod busybox

Name:busybox

Namespace:default

node:k8s-node-1/10.0.0.12

Start Time:thu, June 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 kubelet k8s-node-1} Warning failedsync Error syncing pod, skipping:failed to "Star Tcontainer "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 "Star Tcontainer ' for ' POD ' with errimagepull: ' Image pull failed for registry.access.redhat.com/rhel7/pod-infrastructure:  Latest, this may because there is no credentials on the this request. Details: (open/etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt:no such file or directory) "

see registry.access.redhat.com/rhel7/pod-infrastructure:latest feels strange, I set the warehouse is Grc.io, why go to pull this image, suspect is not what is not installed well. Try to run Docker pull  registry.access.redhat.com /rhel7/pod-infrastructure:latest , prompting redhat-ca.crt:no such file or directory . LS View change file is a soft connection, link target is/ETC/RHSM, see no RHSM, try to install Yum install *rhsm*, the related software, feel more in line with, so installation view produced/etc/rhsm folder.

run Kubectl get again Pods

NAME Ready STATUS Restarts
Redis-master-qhd12 1/1 Running 0 13m

Use Kubernetes to create a container that has been in the containercreating state for reasons of finding and resolving