2017-05-24 36 views
0

我正在谷歌容器引擎上運行k8羣集。我無法讓它從私人碼頭回購中拉出圖像。無法從kubernetes上的私人碼頭中心註冊表中獲取

Name: \t \t ds-expected-date 
 
Namespace: \t default 
 
Node: \t \t gke-ds-cluster-1-default-pool-8980b100-l64j/10.132.0.3 
 
Start Time: \t Wed, 24 May 2017 13:24:11 +0100 
 
Labels: \t \t <none> 
 
Annotations: \t kubernetes.io/limit-ranger=LimitRanger plugin set: cpu request for container ds-expected-date-flask 
 
Status: \t \t Pending 
 
IP: \t \t 10.40.0.23 
 
Controllers: \t <none> 
 
Containers: 
 
    ds-expected-date-flask: 
 
    Container ID: 
 
    Image: \t \t fluidy/ds-expected-date:latest 
 
    Image ID: 
 
    Port: 
 
    State: \t \t Waiting 
 
     Reason: \t \t ImagePullBackOff 
 
    Ready: \t \t False 
 
    Restart Count: \t 0 
 
    Requests: 
 
     cpu: \t \t 100m 
 
    Environment: \t <none> 
 
    Mounts: 
 
     /var/run/secrets/kubernetes.io/serviceaccount from default-token-h340m (ro) 
 
Conditions: 
 
    Type \t \t Status 
 
    Initialized \t True 
 
    Ready \t False 
 
    PodScheduled \t True 
 
Volumes: 
 
    default-token-h340m: 
 
    Type: \t Secret (a volume populated by a Secret) 
 
    SecretName: \t default-token-h340m 
 
    Optional: \t false 
 
QoS Class: \t Burstable 
 
Node-Selectors: \t <none> 
 
Tolerations: \t <none> 
 
Events: 
 
    FirstSeen \t LastSeen \t Count \t From \t \t \t \t \t \t \t SubObjectPath \t \t \t \t Type \t \t Reason \t \t Message 
 
    --------- \t -------- \t ----- \t ---- \t \t \t \t \t \t \t ------------- \t \t \t \t -------- \t ------ \t \t ------- 
 
    21s \t \t 21s \t \t 1 \t default-scheduler \t \t \t \t \t \t \t \t \t \t Normal \t \t Scheduled \t Successfully assigned ds-expected-date to gke-ds-cluster-1-default-pool-8980b100-l64j 
 
    18s \t \t 18s \t \t 1 \t kubelet, gke-ds-cluster-1-default-pool-8980b100-l64j \t spec.containers{ds-expected-date-flask} \t Normal \t \t BackOff \t \t Back-off pulling image "fluidy/ds-expected-date:latest" 
 
    18s \t \t 18s \t \t 1 \t kubelet, gke-ds-cluster-1-default-pool-8980b100-l64j \t \t \t \t \t \t Warning \t \t FailedSync \t Error syncing pod, skipping: failed to "StartContainer" for "ds-expected-date-flask" with ImagePullBackOff: "Back-off pulling image \"fluidy/ds-expected-date:latest\"" 
 

 
    20s \t 6s \t 2 \t kubelet, gke-ds-cluster-1-default-pool-8980b100-l64j \t spec.containers{ds-expected-date-flask} \t Normal \t Pulling \t \t pulling image "fluidy/ds-expected-date:latest" 
 
    19s \t 5s \t 2 \t kubelet, gke-ds-cluster-1-default-pool-8980b100-l64j \t spec.containers{ds-expected-date-flask} \t Warning \t Failed \t \t Failed to pull image "fluidy/ds-expected-date:latest": Error response from daemon: unauthorized: authentication required 
 
    19s \t 5s \t 2 \t kubelet, gke-ds-cluster-1-default-pool-8980b100-l64j \t \t \t \t \t \t Warning \t FailedSync \t Error syncing pod, skipping: failed to "StartContainer" for "ds-expected-date-flask" with ErrImagePull: "Error response from daemon: unauthorized: authentication required"

我按照上the docs page所有指令:

我試圖啓動時得到如下。我相信我的註冊表祕密正在被讀取 - 如果我將duff憑證放入其中,錯誤將更改爲「無效的用戶名或密碼」。

+0

你有一個本地集羣,無論是在流浪或「minikube」風格,以確保祕密值可能工作?這也將有望提供更好,更好的日誌,因爲您隨後可以爲'kubelet','apiserver'或其他任何東西曲柄啓動'--v = 10' –

+1

圖像名稱應該以註冊表名稱?所以名稱應該更多'myregistry.io/fluidy/ds-expected-date:latest',現在好像它試圖從碼頭中心拉圖像? – surajd

+0

絕對看起來@surajd說 –

回答

相關問題