无法拉出映像“/posts:0.0.1”：rpc错误：code=未知desc=来自DAE的错误响应...如何用docker图像修复这个问题？

Question

Pavel@debian:~$kubectl版本客户端版本：version.info{Major:"1“,Minor：”19“,GitVersion:"V1.19.4”,GitCommit:"123“,GitTreest:"Clean”,GitTreest:"Clean“,BuildDate：”2020-11-11T13:17:17z“,GoVersion:"Go1.15.2”,编译器：“GC”,平台：“Linux/AMD64”}服务器版本：version.info{Major:"1“,Minor：”19“,GitVersion:"V1.19.4”,“，编译器：”gc“，平台：”linux/amd64“}

Posts.Yaml

apiVersion: v1
kind: Pod
metadata:
  name: posts
spec:
  containers:
    - name: posts
      image: <mylogin>/posts:0.0.1

kubectl apply-f posts.yaml

Debian:~$kubectl描述pod帖子

Name:         posts
Namespace:    default
Priority:     0
Node:         minikube/192.168.49.2
Start Time:   Wed, 25 Nov 2020 07:06:47 +0400
Labels:       <none>
Annotations:  <none>
Status:       Pending
IP:           172.17.0.4
IPs:
  IP:  172.17.0.4
Containers:
  posts:
    Container ID:   
    Image:          <mylogin>/posts:0.0.1
    Image ID:       
    Port:           <none>
    Host Port:      <none>
    State:          Waiting
      Reason:       ImagePullBackOff
    Ready:          False
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-b9gkg (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  default-token-b9gkg:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-b9gkg
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  23m                   default-scheduler  Successfully assigned default/posts to minikube
  Normal   Pulling    21m (x4 over 23m)     kubelet            Pulling image "<mylogin>/posts:0.0.1"
  Warning  Failed     21m (x4 over 23m)     kubelet            Failed to pull image "<mylogin>/posts:0.0.1": rpc error: code = Unknown desc = Error response from daemon: pull access denied for <mylogin>/posts, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
  Warning  Failed     21m (x4 over 23m)     kubelet            Error: ErrImagePull
  Warning  Failed     7m53s (x63 over 23m)  kubelet            Error: ImagePullBackOff
  Normal   BackOff    2m58s (x84 over 23m)  kubelet            Back-off pulling image "<mylogin>/posts:0.0.1"

Answer 1

Minikube无法直接访问您的本地docker存储库。有几种方法可以解决这个问题，下面详细介绍它们:https://minikube.sigs.k8s.io/docs/handbook/pushing/

就我个人而言，我只是使用Minikube cache add将图像添加到Minikube缓存中，然后需要将yaml文件中的ImagePullPolicy更改为Never。这样，它将默认使用缓存到MiniKube中的本地映像。您也可以在添加缓存后重新加载它。如果在将容器添加到集群之前使用Docker测试容器，这可能是最简单的方法。

您也可以尝试其他方法，包括使用Minikube内的守护进程直接构建容器映像。