关于k8s起pod报错：details(open /etc/doc..no such file

一.报错环境：

1. 创建了RC文件，kubectl get pods显示 pod一直处于ContainerCreating
2. kubectl describe pod mysql-3k3x0

发现：

报错：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)"

分析：1.image pullbackoff 镜像拉取失败（docker images 已存在该镜像，排除）

2.details: (open /etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt: no such file or directory)"（已定位）

二.解决方案

1. /etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt是一个软连接指向/etc/rhsm/ca/redhat-uep.pem，但实际并不存在所以需要：yum insall -y *rhsm*

wget http://mirror.centos.org/centos/7/os/x86_64/Packages/python-rhsm-certificates-1.19.10-1.el7_4.x86_64.rpm rpm2cpio python-rhsm-certificates-1.19.10-1.el7_4.x86_64.rpm | cpio -iv --to-stdout ./etc/rhsm/ca/redhat-uep.pem | tee /etc/rhsm/ca/redhat-uep.pem

docker pull registry.access.redhat.com/rhel7/pod-infrastructure:latest

2. 重新启动kubelet服务

systemctl restart kubelet

3. 删除原来的RC文件

kubectl delete -f mysql-rc.yaml(若删除不了直接rm -f)

4. 重新生成新的RC文件

5. 查看效果并能正常启动

kubectl get pods