kubernetes为echo服务器抛出CrashLoopBackOff
我想在我的kubernetes集群上部署starter映像 我有三颗树莓，一簇一簇的kubernetes为echo服务器抛出CrashLoopBackOff,kubernetes,Kubernetes,我想在我的kubernetes集群上部署starter映像 我有三颗树莓，一簇一簇的 > kubectl version -o json ~ { "clientVersion": {
> kubectl version -o json ~
{
"clientVersion": {
"major": "1",
"minor": "18",
"gitVersion": "v1.18.2",
"gitCommit": "52c56ce7a8272c798dbc29846288d7cd9fbae032",
"gitTreeState": "clean",
"buildDate": "2020-04-16T11:56:40Z",
"goVersion": "go1.13.9",
"compiler": "gc",
"platform": "linux/arm"
},
"serverVersion": {
"major": "1",
"minor": "18",
"gitVersion": "v1.18.2",
"gitCommit": "52c56ce7a8272c798dbc29846288d7cd9fbae032",
"gitTreeState": "clean",
"buildDate": "2020-04-16T11:48:36Z",
"goVersion": "go1.13.9",
"compiler": "gc",
"platform": "linux/arm"
}
}
> docker -v ~
Docker version 19.03.8, build afacb8b
> kubectl get node ~
NAME STATUS ROLES AGE VERSION
master-pi4 Ready master 18h v1.18.2
node1-pi4 Ready <none> 17h v1.18.2
node2-pi3 Ready <none> 17h v1.18.2
kubectl describe pod hello-node ~
Name: hello-node-7bf657c596-wc5r4
Namespace: default
Priority: 0
Node: node1-pi4/192.168.188.11
Start Time: Wed, 13 May 2020 15:02:10 +0200
Labels: app=hello-node
pod-template-hash=7bf657c596
Annotations: <none>
Status: Running
IP: 10.32.0.4
IPs:
IP: 10.32.0.4
Controlled By: ReplicaSet/hello-node-7bf657c596
Containers:
echoserver:
Container ID: docker://841beb3a675963ecb40569439e0575a29c5b9f48aaa967da8c011faeafd96acc
Image: k8s.gcr.io/echoserver:1.4
Image ID: docker-pullable://k8s.gcr.io/echoserver@sha256:5d99aa1120524c801bc8c1a7077e8f5ec122ba16b6dda1a5d3826057f67b9bcb
Port: <none>
Host Port: <none>
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Wed, 13 May 2020 15:18:03 +0200
Finished: Wed, 13 May 2020 15:18:03 +0200
Ready: False
Restart Count: 8
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-wvbzk (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
default-token-wvbzk:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-wvbzk
Optional: false
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled <unknown> default-scheduler Successfully assigned default/hello-node-7bf657c596-wc5r4 to node1-pi4
Normal Pulled 15m (x5 over 16m) kubelet, node1-pi4 Container image "k8s.gcr.io/echoserver:1.4" already present on machine
Normal Created 15m (x5 over 16m) kubelet, node1-pi4 Created container echoserver
Normal Started 15m (x5 over 16m) kubelet, node1-pi4 Started container echoserver
Warning BackOff 112s (x70 over 16m) kubelet, node1-pi4 Back-off restarting failed container
kubectl描述pod hello节点~
名称：hello-node-7bf657c596-wc5r4
名称空间：默认值
优先级：0
节点：节点1-pi4/192.168.188.11
开始时间：2020年5月13日星期三15:02:10+0200
标签：app=hello节点
pod模板哈希=7bf657c596
注释：
状态：正在运行
IP:10.32.0.4
IPs：
IP:10.32.0.4
控制人：ReplicaSet/hello-node-7bf657c596
容器：
echoserver：
容器ID:docker://841beb3a675963ecb40569439e0575a29c5b9f48aaa967da8c011faeafd96acc
图片：k8s.gcr.io/echoserver:1.4
图像ID:docker-pullable://k8s.gcr.io/echoserver@sha256:5d99aa1120524c801bc8c1a7077e8f5ec122ba16b6dda1a5d3826057f67b9bcb
端口：
主机端口：
国家：等待
原因：仓促退却
最后状态：终止
原因：错误
退出代码：1
开始日期：2020年5月13日星期三15:18:03+0200
完成日期：2020年5月13日星期三15:18:03+0200
就绪：错误
重新启动计数：8
环境：
挂载：
/来自默认令牌wvbzk（ro）的var/run/secrets/kubernetes.io/serviceaccount
条件：
类型状态
初始化为True
准备错误
集装箱准备好了吗
播客预定为真
卷数：
默认令牌wvbzk：
类型：Secret（由Secret填充的卷）
SecretName：默认令牌wvbzk
可选：false
QoS等级：最佳努力
节点选择器：
容差：node.kubernetes.io/未就绪：不执行300秒
node.kubernetes.io/不可访问：不执行300秒
活动：
从消息中键入原因年龄
---- ------ ---- ---- -------
正常调度的默认计划程序已成功将默认/hello-node-7bf657c596-wc5r4分配给node1-pi4
正常牵引15米（x5/16米）kubelet，机器上已存在节点1-pi4容器映像“k8s.gcr.io/echoserver:1.4”
正常创建15m（x5/16m）kubelet，节点1-pi4创建容器echoserver
正常启动15m（x5/16m）kubelet，节点1-pi4启动容器服务器
警告后退112s（x70超过16m）kubelet，节点1-pi4后退重新启动失败的容器
我遗漏了什么？这可能是因为此映像与ARM体系结构不兼容
您应该改为使用此映像
k8s.gcr.io/echoserver arm:1.8您应该改为使用此图像
k8s.gcr.io/echoserver arm:1.8kubectl logs[podname]-pkubectl logs[podname]-pkubectl describe pod hello-node ~
Name: hello-node-7bf657c596-wc5r4
Namespace: default
Priority: 0
Node: node1-pi4/192.168.188.11
Start Time: Wed, 13 May 2020 15:02:10 +0200
Labels: app=hello-node
pod-template-hash=7bf657c596
Annotations: <none>
Status: Running
IP: 10.32.0.4
IPs:
IP: 10.32.0.4
Controlled By: ReplicaSet/hello-node-7bf657c596
Containers:
echoserver:
Container ID: docker://841beb3a675963ecb40569439e0575a29c5b9f48aaa967da8c011faeafd96acc
Image: k8s.gcr.io/echoserver:1.4
Image ID: docker-pullable://k8s.gcr.io/echoserver@sha256:5d99aa1120524c801bc8c1a7077e8f5ec122ba16b6dda1a5d3826057f67b9bcb
Port: <none>
Host Port: <none>
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Wed, 13 May 2020 15:18:03 +0200
Finished: Wed, 13 May 2020 15:18:03 +0200
Ready: False
Restart Count: 8
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-wvbzk (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
default-token-wvbzk:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-wvbzk
Optional: false
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled <unknown> default-scheduler Successfully assigned default/hello-node-7bf657c596-wc5r4 to node1-pi4
Normal Pulled 15m (x5 over 16m) kubelet, node1-pi4 Container image "k8s.gcr.io/echoserver:1.4" already present on machine
Normal Created 15m (x5 over 16m) kubelet, node1-pi4 Created container echoserver
Normal Started 15m (x5 over 16m) kubelet, node1-pi4 Started container echoserver
Warning BackOff 112s (x70 over 16m) kubelet, node1-pi4 Back-off restarting failed container