kubernetes：容器没有开始使用私有registry

我有一个运行在debian上的kubernetes 1.1.1的工作安装

我也有一个私人registry工作正常运行在V2 ..

我面临一个奇怪的问题。

在master中定义一个pod

apiVersion：v1 kind：Pod元数据：name：nginx标签：app：nginx spec：容器： – name：nginx图片：docker-registry.hiberus.com:5000/debian:ssh imagePullSecrets： – name：myregistrykey

我也有我的主人myregistrykey kubernetes.io/dockercfg 1 44米的秘密

和我的config.json是这样的

{ "auths": { "https://docker-registry.hiberus.com:5000": { "auth": "anNhdXJhOmpzYXVyYQ==", "email": "[e-mail]" } } } 

所以我做了base64并创build了我的秘密。

简单如地狱

在我的节点上的图像被拖动没有任何问题

 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 

它在内部循环试图启动，但从来没有

奇怪的是，如果y手动执行我的节点上的运行命令容器启动没有任何问题，但使用pod拉图像，但从来没有启动..

难道我做错了什么？

如果我使用公共图像为我的吊舱，它启动没有任何问题..这只发生在使用私人图像时

我也从Debian搬到Ubuntu，没有运气同样的问题

我也把这个秘密联系到了默认的服务帐号，还是没有运气

克隆了最后的git版本，编译，没有运气..

我很清楚，问题是使用私人registry，但是我已经应用并遵循了所有我已阅读的信息，但仍然没有运气。