kubernetes :未开始使用专用注册表的容器

Question

我在debian上运行了kubernetes 1.1.1的工作安装

我还拥有一个在v2中运行良好的私有注册表。

我正面临着一个奇怪的问题。

在师父身上定义一个吊舱

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的秘密

我的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

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

奇怪的是，如果y在我的节点上手动执行一个run命令，容器就会启动，没有任何问题，但是使用吊舱可以拉出图像，但从未启动。

我做错什么了吗？

如果我用一个公众形象作为我的吊舱，它就开始了，没有任何问题。只有当我使用私人图片时才会发生这种情况。

我也从debian搬到了ubuntu，没有运气的问题。

我还把这个秘密链接到了帐户，仍然没有运气。

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

很明显，问题是使用私人注册表，但我已经申请和跟踪所有的信息，我已经阅读，但仍然没有运气。

Answer 1

一个码头容器可以退出，如果它的主要进程有退出。你能共享集装箱日志吗？

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

参考- Why docker container exits immediately