kubernetes：容器未開始使用私有注冊表

Question

我有一個在 debian 上運行的 kubernetes 1.1.1 的工作安裝

我還有一個在 v2 中運行良好的私有注冊表..

我正面臨一個奇怪的問題。

在 master 中定義一個 pod

apiVersion: v1
kind: Pod
metadata:
name: nginx
labels:
app: nginx
spec:
containers:
- name: nginx
image: docker-registry.hiberus.com:5000/debian:ssh
imagePullSecrets:
- name: myregistrykey

我的主myregistrykey kubernetes.io/dockercfg 1 44m上也有秘密myregistrykey kubernetes.io/dockercfg 1 44m

我的 config.json 就是這樣制作的

{
"auths": {
"https://docker-registry.hiberus.com:5000": {
"auth": "anNhdXJhOmpzYXVyYQ==",
"email": "jsaura@heraldo.es"
}
}
}

所以我做了 base64 並創建了我的秘密。

簡單到地獄

在我的節點上，圖像被拉出沒有任何問題

docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
docker-registry.hiberus.com:5000/debian ssh 3b332951c107 29 minutes ago 183.3 MB
golang 1.4 2819d1d84442 7 days ago 562.7 MB
debian latest 91bac885982d 8 days ago 125.1 MB
gcr.io/google_containers/pause 0.8.0 2c40b0526b63 7 months ago 241.7 kB

但我的容器沒有啟動

./kubectl describe pod nginx
Name: nginx
Namespace: default
Image(s): docker-registry.hiberus.com:5000/debian:ssh
Node: 192.168.29.122/192.168.29.122
Start Time: Wed, 18 Nov 2015 17:08:53 +0100
Labels: app=nginx
Status: Running
Reason:
Message:
IP: 172.17.0.2
Replication Controllers: 
Containers:
nginx:
Container ID: docker://3e55ab118a3e5d01d3c58361abb1b23483d41be06741ce747d4c20f5abfeb15f
Image: docker-registry.hiberus.com:5000/debian:ssh
Image ID: docker://3b332951c1070ba2d7a3bb439787a8169fe503ed8984bcefd0d6c273d22d4370
State: Waiting
Reason: CrashLoopBackOff
Last Termination State: Terminated
Reason: Error
Exit Code: 0
Started: Wed, 18 Nov 2015 17:08:59 +0100
Finished: Wed, 18 Nov 2015 17:08:59 +0100
Ready: False
Restart Count: 2
Environment Variables:
Conditions:
Type Status
Ready False
Volumes:
default-token-ha0i4:
Type: Secret (a secret that should populate this volume)
SecretName: default-token-ha0i4
Events:
FirstSeen LastSeen Count From SubobjectPath Reason Message
───────── ──────── ───── ──── ───────────── ────── ───────
16s 16s 1 {kubelet 192.168.29.122} implicitly required container POD Created Created with docker id 4a063be27162
16s 16s 1 {kubelet 192.168.29.122} implicitly required container POD Pulled Container image "gcr.io/google_containers/pause:0.8.0" already present on machine
16s 16s 1 {kubelet 192.168.29.122} implicitly required container POD Started Started with docker id 4a063be27162
16s 16s 1 {kubelet 192.168.29.122} spec.containers{nginx} Pulling Pulling image "docker-registry.hiberus.com:5000/debian:ssh"
15s 15s 1 {scheduler } Scheduled Successfully assigned nginx to 192.168.29.122
11s 11s 1 {kubelet 192.168.29.122} spec.containers{nginx} Created Created with docker id 36df2dc8b999
11s 11s 1 {kubelet 192.168.29.122} spec.containers{nginx} Pulled Successfully pulled image "docker-registry.hiberus.com:5000/debian:ssh"
11s 11s 1 {kubelet 192.168.29.122} spec.containers{nginx} Started Started with docker id 36df2dc8b999
10s 10s 1 {kubelet 192.168.29.122} spec.containers{nginx} Pulled Container image "docker-registry.hiberus.com:5000/debian:ssh" already present on machine
10s 10s 1 {kubelet 192.168.29.122} spec.containers{nginx} Created Created with docker id 3e55ab118a3e
10s 10s 1 {kubelet 192.168.29.122} spec.containers{nginx} Started Started with docker id 3e55ab118a3e
5s 5s 1 {kubelet 192.168.29.122} spec.containers{nginx} Backoff Back-off restarting failed docker container

它在內部循環嘗試啟動，但從未啟動

奇怪的是，如果你在我的節點上手動執行運行命令，容器啟動沒有任何問題，但使用 pod 拉圖像但從未啟動..

難道我做錯了什么？

如果我為我的 pod 使用公共圖像，它啟動時沒有任何問題..這只會在使用私有圖像時發生在我身上..

我也從 debian 轉移到 ubuntu，沒有運氣同樣的問題

我還將秘密鏈接到默認服務帳戶，仍然沒有運氣

克隆了最后一個 git 版本，編譯，沒有運氣..

對我來說很明顯問題是使用私有注冊表，但我已經申請並遵循了我閱讀的所有信息，但仍然沒有運氣。

Answer 1

如果 docker 容器的主進程已退出，則它可能會退出。 你能分享容器日志嗎？

1. 如果你執行docker ps -a你應該看到所有正在運行和退出的容器
2. 運行docker container logs container_id

還嘗試以交互和守護程序模式運行您的容器，看看它是否僅在守護程序模式下失敗。

在守護進程模式下運行 -

docker run -d -t Image_name

以交互模式運行 -

docker run -it Image_name

對於交互式守護進程模式docker run -idt Image_name

參考 - 為什么 docker 容器會立即退出