Docker本地存储库在节点重新启动后不工作

k8s主节点重新启动后，docker本地存储库服务器无法正常工作

存储库服务器存在，并已分配与最初工作的IP相同的IP，并已添加到docker daemon.json上。存储库卷也可用

在运行命令“sudo docker compose up”后，成功地从并行终端“Ctrl C”卷曲，重新创建和标记图像，我再次能够从本地存储库推拉图像，POD开始按预期运行

码头工人详情 版本：19.03.6 API版本：1.40 Go版本：go1.12.17 Git提交：369ce74a3c 建成日期：2020年2月28日星期五23:45:43 OS/Arch:linux/amd64 实验性：错误

服务器： 发动机： 版本：19.03.6 API版本：1.40（最低版本1.12） Go版本：go1.12.17 Git提交：369ce74a3c 建成日期：星期三2月19日01:06:16 2020 OS/Arch:linux/amd64 实验性：错误 集装箱： 版本：1.3.3-0ubuntu1~18.04.1 GitCommit： runc: 版本：spec:1.0.1-dev GitCommit： docker初始化： 版本：0.18.0 GitCommit：

对我来说，这看起来像一个docker守护程序错误，如果是这样，是否有任何适当的/永久的修复这个问题

~$ kubectl get pods,svc,pvc,pv,deployment
NAME READY STATUS RESTARTS AGE
pod/nginx-595f85746d-w8khf 1/1 Running 4 2d23h
pod/registry-cbc9b4779-nhf5f 1/1 Running 4 2d23h
pod/try1-7f766ff65-7x79x 0/1 ImagePullBackOff 0 19h
pod/try1-7f766ff65-fpzpx 0/1 ImagePullBackOff 0 19h
pod/try1-7f766ff65-hq7ql 0/1 ImagePullBackOff 0 19h
pod/try1-7f766ff65-j7nh2 0/1 ImagePullBackOff 0 19h
pod/try1-7f766ff65-vzcsk 0/1 ImagePullBackOff 0 19h
pod/try1-7f766ff65-x646d 0/1 ImagePullBackOff 0 19h


$ kubectl describe pod try1-7f766ff65-x646d
Name: try1-7f766ff65-x646d
Namespace: default
Priority: 0
Node: kw1/...
Start Time: Tue, 07 Apr 2020 01:46:05 +0000
Labels: app=try1
pod-template-hash=7f766ff65
Annotations: cni.projectcalico.org/podIP: 192.168.159.102/32
Status: Pending
IP: 192.168.159.102
IPs:
IP: 192.168.159.102
Controlled By: ReplicaSet/try1-7f766ff65
Containers:
simpleapp:
Container ID:
Image: 10.107.241.131:5000/simpleapp:latest
Image ID:
Port:
Host Port:
State: Waiting
Reason: ImagePullBackOff
Ready: False
Restart Count: 0
Readiness: exec [cat /tmp/healthy] delay=0s timeout=1s period=5s #success=1 #failure=3
Environment:
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-zqbsw (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
default-token-zqbsw:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-zqbsw
Optional: false
QoS Class: BestEffort
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 25h default-scheduler Successfully assigned default/try1-7f766ff65-x646d to kw1
Normal Pulling 25h kubelet, kw1 Pulling image "10.107.241.131:5000/simpleapp:latest"
Normal Pulled 25h kubelet, kw1 Successfully pulled image "10.107.241.131:5000/simpleapp:latest"
Normal Created 25h kubelet, kw1 Created container simpleapp
Normal Started 25h kubelet, kw1 Started container simpleapp
Warning Unhealthy 25h (x120 over 25h) kubelet, kw1 Readiness probe failed: cat: /tmp/healthy: No such file or directory
Warning FailedCreatePodSandBox 4m48s kubelet, kw1 Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "3c107122748a2d99f9f89e92d960d939c29392fbf94f28761c1cdce66240b844" network for pod "try1-7f766ff65-x646d": networkPlugin cni failed to set up pod "try1-7f766ff65-x646d_default" network: error getting ClusterInformation: Get https://[10.96.0.1]:443/apis/crd.projectcalico.org/v1/clusterinformations/default: dial tcp 10.96.0.1:443: i/o timeout
Normal SandboxChanged 4m47s kubelet, kw1 Pod sandbox changed, it will be killed and re-created.
Warning Failed 4m32s kubelet, kw1 Failed to pull image "10.107.241.131:5000/simpleapp:latest": rpc error: code = Unknown desc = Error response from daemon: Get http://10.107.241.131:5000/v2/: dial tcp 10.107.241.131:5000: connect: no route to host
Normal BackOff 3m15s (x5 over 4m31s) kubelet, kw1 Back-off pulling image "10.107.241.131:5000/simpleapp:latest"
Normal Pulling 3m2s (x4 over 4m45s) kubelet, kw1 Pulling image "10.107.241.131:5000/simpleapp:latest"
Warning Failed 3m2s (x4 over 4m32s) kubelet, kw1 Error: ErrImagePull
Warning Failed 3m2s (x3 over 4m19s) kubelet, kw1 Failed to pull image "10.107.241.131:5000/simpleapp:latest": rpc error: code = Unknown desc = Error response from daemon: manifest for 10.107.241.131:5000/simpleapp:latest not found: manifest unknown: manifest unknown
Warning Failed 2m47s (x6 over 4m31s) kubelet, kw1 Error: ImagePullBackOff

---

检查你的docker图像，似乎它无法提取你的docker图像 如果您使用minikube，只需键入

minikube start --insecure-registry=<URHOST>:5000 

minikube启动--不安全注册表=：5000

或编辑/etc/default/docker并添加

 DOCKER_OPTS="--insecure-registry <URHOST>:5000"

DOCKER_OPTS=“--不安全的注册表：5000”

能否尝试在本地提取图像？docker pull 10.107.241.131:5000/simpleapp:latestNo，当主节点重新启动后出现问题时，我无法在本地拉取映像。我认为您正在将注册表作为容器运行。在主节点重新启动后再次启动注册表容器，并尝试在本地拉取映像。Manel，我的注册表添加到主节点的/etc/docker/daemon.json中。我没有文件/etc/default/dockerThis是一个未安装minikube的k8s主节点设置，我有所有kubernetes和docker命令。