kubernetes不能拉当地形象

问题描述 投票:12回答:4

我在一台机器上使用kubernetes进行测试,我已经从nginx docker图像构建了一个自定义图像,但是当我尝试在kubernetes中使用图像时,我得到一个图像拉错误?????

我的POD YAML

kind: Pod
apiVersion: v1
metadata:
  name: yumserver
  labels:
    name: frontendhttp
spec:
  containers:
    - name: myfrontend
      image: my/nginx:latest
      ports:
        - containerPort: 80
          name: "http-server"
      volumeMounts:
      - mountPath: "/usr/share/nginx/html"
        name: mypd
  imagePullSecrets:
    - name: myregistrykey

  volumes:
    - name: mypd
      persistentVolumeClaim:
       claimName: myclaim-1

我的KUBERNET命令

kubectl create -f pod-yumserver.yaml

错误

kubectl describe pod yumserver


Name: yumserver
Namespace: default
Image(s):   my/nginx:latest
Node:       127.0.0.1/127.0.0.1
Start Time: Tue, 26 Apr 2016 16:31:42 +0100
Labels:     name=frontendhttp
Status:     Pending
Reason:     
Message:    
IP:     172.17.0.2
Controllers:    <none>
Containers:
  myfrontend:
    Container ID:   
    Image:      my/nginx:latest
    Image ID:       
    QoS Tier:
      memory:       BestEffort
      cpu:      BestEffort
    State:      Waiting
      Reason:       ErrImagePull
    Ready:      False
    Restart Count:  0
    Environment Variables:
Conditions:
  Type      Status
  Ready     False 
Volumes:
  mypd:
    Type:   PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  myclaim-1
    ReadOnly:   false
  default-token-64w08:
    Type:   Secret (a secret that should populate this volume)
    SecretName: default-token-64w08
Events:
  FirstSeen LastSeen    Count   From            SubobjectPath           Type        Reason          Message
  --------- --------    -----   ----            -------------           --------    ------          -------
  13s       13s     1   {default-scheduler }                    Normal      Scheduled       Successfully assigned yumserver to 127.0.0.1
  13s       13s     1   {kubelet 127.0.0.1}                 Warning     MissingClusterDNS   kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. Falling back to DNSDefault policy.
  12s       12s     1   {kubelet 127.0.0.1} spec.containers{myfrontend} Normal      Pulling         pulling image "my/nginx:latest"
  8s        8s      1   {kubelet 127.0.0.1} spec.containers{myfrontend} Warning     Failed          Failed to pull image "my/nginx:latest": Error: image my/nginx:latest not found
  8s        8s      1   {kubelet 127.0.0.1}                 Warning     FailedSync      Error syncing pod, skipping: failed to "StartContainer" for "myfrontend" with ErrImagePull: "Error: image my/nginx:latest not found"
docker kubernetes docker-registry
4个回答
17
投票

所以你的机器上有图像。它仍然试图从Docker Hub中提取图像,但这可能不是你想要的单机设置。发生这种情况是因为最新标记将imagePullPolicy设置为Always隐式。您可以尝试将其明确设置为IfNotPresent或更改为最新以外的标记。 - Timo Reimann 4月28日7:16

出于某种原因,Timo Reimann只是将上述内容作为评论发布,但它肯定应该是这个问题的正式答案,所以我再次发布它。


15
投票

在构建映像之前运行eval $(minikube docker-env)。

完整答案:https://stackoverflow.com/a/40150867


4
投票

进一步分析ErrImagePull问题的最简单方法是ssh到节点并尝试通过执行docker pull my/nginx:latest手动拉取图像。我从来没有在一台机器上设置Kubernetes,但可以想象由于某种原因无法从节点访问Docker守护程序。试图拉动尝试应该提供更多信息。


1
投票

你在linux上使用minikube吗?你需要安装docker(我认为),但你不需要启动它。 Minikube会做到这一点。尝试使用此命令使用KVM驱动程序:

minikube start --vm-driver kvm

然后运行eval $(minikube docker-env)命令以确保使用minikube docker环境。使用标签build -t mycontainername:version .构建容器

如果然后键入docker ps,你应该会看到一堆已经运行的minikube容器。 kvm utils可能已经在你的机器上,但它们可以像centos / rhel一样安装:

yum install qemu-kvm qemu-img virt-manager libvirt libvirt-python 
© www.soinside.com 2019 - 2024. All rights reserved.