1. 程式人生 > >k8s 安裝報錯details: (open /etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt: no such file or

k8s 安裝報錯details: (open /etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt: no such file or

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檔案.

順得的話會得到下面的結果。

 

[[email protected]]# 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

[[email protected] /]# kubectl delete -f mysql-rc.yaml

重新建立

[[email protected] /]# kubectl create -f mysql-rc.yaml

replicationcontroller "mysql" created

再次檢視狀態

[[email protected] /]# kubectl get pod

NAME READY STATUS RESTARTS AGE

mysql-b8m2q 1/1 Running 0 27m