Symptom:
We follow the Oracle Kubernetes Doc to install kubeadm. The kubeadm-setup.sh has added "region" in the code to connect container registry of each region.ie; Phoenix, it will contact container-registry-phx.oracle.com/kubernetes
However we have problems to pull images from it for latest 1.10.5 which is developer release
Error like
#kubeadm-setup.sh up
Starting to initialize master node ...
Checking if env is ready ...
Checking whether docker can pull busybox image ...
Checking access to container-registry-phx.oracle.com/kubernetes ...
Trying to pull repository container-registry-phx.oracle.com/kubernetes/kube-proxy-amd64 ...
manifest for container-registry-phx.oracle.com/kubernetes/kube-proxy-amd64:v1.10.5 not found
[ERROR] docker cannot pull kube-proxy-amd64:v1.10.5 from container-registry-phx.oracle.com/kubernetes registry
Solution:
To set env parameter to specify registry we would like to connect:#export KUBE_REPO_PREFIX=container-registry.oracle.com/kubernetes_developer
and rerun the kubeadm-setup.sh
Meanwhile if we want to install 1.9.1 instead, you probably have to disable the preview and developer yum repos to let yum to find old but stable version
No comments:
Post a Comment