本文主要是介绍k8s 安装报错details: (open /etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt: no such file o，希望对大家解决编程问题提供一定的参考价值，需要的开发者们随着小编来一起学习吧！
http://blog.51cto.com/12482328/2120035
其中最主要的问题是：details: (open /etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt: no such file or directory)
解决方案：
查看/etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt （该链接就是上图中的说明） 是一个软链接，但是链接过去后并没有真实的/etc/rhsm，所以需要使用yum安装：
yum install rhsm
安装完成后，执行一下docker pull registry.access.redhat.com/rhel7/pod-infrastructure:latest
如果依然报错，可参考下面的方案：
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
这两个命令会生成/etc/rhsm/ca/redhat-uep.pem文件.
顺得的话会得到下面的结果。
[root@localhost]# docker pull registry.access.redhat.com/rhel7/pod-infrastructure:latest
Trying to pull repository registry.access.redhat.com/rhel7/pod-infrastructure …
latest: Pulling from registry.access.redhat.com/rhel7/pod-infrastructure
26e5ed6899db: Pull complete
66dbe984a319: Pull complete
9138e7863e08: Pull complete
Digest: sha256:92d43c37297da3ab187fc2b9e9ebfb243c1110d446c783ae1b989088495db931
Status: Downloaded newer image for registry.access.redhat.com/rhel7/pod-infrastructure:latest
删除原来创建的rc
[root@localhost /]# kubectl delete -f mysql-rc.yaml
重新创建
[root@localhost /]# kubectl create -f mysql-rc.yaml
replicationcontroller “mysql” created
再次查看状态
[root@localhost /]# kubectl get pod
NAME READY STATUS RESTARTS AGE
mysql-b8m2q 1/1 Running 0 27m
这篇关于k8s 安装报错details: (open /etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt: no such file o的文章就介绍到这儿，希望我们推荐的文章对编程师们有所帮助！
