[英]K8s Error: ImagePullBackOff || read: connection refused
Can you please assist when deploying we getting ImagePullBackOff for our pods.在部署我们为我们的 Pod 获取 ImagePullBackOff 时,您能否提供帮助。
running kubectl get <pod-name> -n namespace -o yaml
am getting below error.运行
kubectl get <pod-name> -n namespace -o yaml
出现以下错误。
containerStatuses:
- image: mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644
imageID: ""
lastState: {}
name: dmd-base
ready: false
restartCount: 0
started: false
state:
waiting:
message: Back-off pulling image "mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644"
reason: ImagePullBackOff
hostIP: x.x.x.53
phase: Pending
podIP: x.x.x.237
and running kubectl describe pod <pod-name> -n namespace
am getting below error infomation并运行
kubectl describe pod <pod-name> -n namespace
低于错误信息
Normal Scheduled 85m default-scheduler Successfully assigned dmd-int/app-app-base-5b4b75756c-lrcp6 to aks-agentpool-35064155-vmss00000a
Warning Failed 85m kubelet Failed to pull image "mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644":
[rpc error: code = Unknown desc = failed to pull and unpack image "mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644":
failed to resolve reference "mycontainer-registry.io/commpany/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644":
failed to do request: Head "https://mycontainer-registry.azurecr.io/v2/company/my-app/manifests/1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644":
dial tcp: lookup mycontainer-registry.azurecr.io on [::1]:53: read udp [::1]:56109->[::1]:53: read: connection refused,
rpc error: code = Unknown desc = failed to pull and unpack image "mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644":
failed to resolve reference "mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644":
failed to do request: Head "https://mycontainer-registry.io/v2/company/my-app/manifests/1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644":
dial tcp: lookup mycontainer-registry.io on [::1]:53: read udp [::1]:60759->[::1]:53: read: connection refused]`
From the described logs I can see the issue is a connection but I can't tell where the issue is with connectivity, we running our apps in a Kubernetes cluster on Azure.从所描述的日志中,我可以看到问题是连接问题,但我无法判断连接问题出在哪里,我们在 Azure 上的 Kubernetes 集群中运行我们的应用程序。
If anyone has come across this issue can you please assist the application has been running successfully throughout the past months we just got this issue this morning.如果有人遇到此问题,请您协助该应用程序在过去几个月中成功运行,我们今天早上刚刚收到此问题。
There is a known Azure outage multiple regions today.今天有一个已知的 Azure 中断多个区域。 Some DNS issue that also affects image pulls.
一些 DNS 问题也会影响图像拉取。 https://status.azure.com/en-us/status
https://status.azure.com/en-us/status
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.