首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >kubectl描述荚部-im-54cbb55ccb-mjl6q

kubectl描述荚部-im-54cbb55ccb-mjl6q
EN

Stack Overflow用户
提问于 2022-01-01 12:07:53
回答 2查看 186关注 0票数 0

一旦我安装并运行它,我也安装了kubernetes,然后我安装了minikube并启动它。我通过kubectl创建部署创建了一些部署--当我得到这些结果时,图像=imageName imageName,我想要一个我试图理解kubernetes错误的解决方案,但是我没有,当我得到豆荚时,得到这些:

代码语言:javascript
复制
PS C:\Users\ahmed> kubectl get pods
NAME                        READY   STATUS         RESTARTS   AGE
depl-im-54cbb55ccb-mjl6q    0/1     ErrImagePull   0          86m
ngnix-app-8d489bb64-tlvrn   0/1     ErrImagePull   0          15h

当描述一个(,如‘ngnix 8d489bb64-tlvrn’)时,我得到:

代码语言:javascript
复制
PS C:\Users\ahmed> kubectl describe pod depl-im-54cbb55ccb-mjl6q

Name:depl-im-54cbb55ccb-mjl6q

Namespace:    default

Priority:     0

Node:         minikube/192.168.49.2

Start Time:   Sat, 01 Jan 2022 12:26:05 +0200

Labels:       app=depl-im
              pod-template-hash=54cbb55ccb

Annotations:  <none>
Status:       Pending

IP:           172.17.0.4
IPs:
  IP:           172.17.0.4
Controlled By:  ReplicaSet/depl-im-54cbb55ccb

Containers:
  depl-im:
    Container ID:
    Image:          depl-im
    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 kube-api-access-b9f8h (ro)

Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True

Volumes:
  kube-api-access-b9f8h:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
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       86m                  default-scheduler  Successfully assigned default/depl-im-54cbb55ccb-mjl6q to minikube
  Normal   Pulling         84m (x4 over 86m)    kubelet            Pulling image "depl-im"
  Warning  Failed          84m (x4 over 86m)    kubelet            Failed to pull image "depl-im": rpc error: code = Unknown desc = Error response from daemon: pull access denied for depl-im, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
  Warning  Failed          84m (x4 over 86m)    kubelet            Error: ErrImagePull
  Warning  Failed          84m (x6 over 86m)    kubelet            Error: ImagePullBackOff
  Normal   BackOff         56m (x128 over 86m)  kubelet            Back-off pulling image "depl-im"
  Normal   SandboxChanged  114s                 kubelet            Pod sandbox changed, it will be killed and re-created.
  Normal   BackOff         33s (x2 over 61s)    kubelet            Back-off pulling image "depl-im"
  Warning  Failed          33s (x2 over 61s)    kubelet            Error: ImagePullBackOff
  Normal   Pulling         18s (x3 over 80s)    kubelet            Pulling image "depl-im"
  Warning  Failed          15s (x3 over 62s)    kubelet            Failed to pull image "depl-im": rpc error: code = Unknown desc = Error response from daemon: pull access denied for depl-im, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
  Warning  Failed          15s (x3 over 62s)    kubelet            Error: ErrImagePull
EN

回答 2

Stack Overflow用户

发布于 2022-01-01 16:31:55

如果kubernetes试图拉的这个映像是由私有映像存储库承载的,那么您需要将包含凭据的秘密放置在部署/吊舱所在的kubernetes名称空间中。

然后,使用

代码语言:javascript
复制
imagePullSecrets:
  - name: secret-name

在你的部署规范中。

参考:https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/

如果您试图在Kubernetes中使用本地构建的码头映像,请查看以下内容:https://medium.com/swlh/how-to-run-locally-built-docker-images-in-kubernetes-b28fbc32cc1d

票数 1
EN

Stack Overflow用户

发布于 2022-01-01 15:32:59

请使用以下命令首先登录图像所在的存储库:

代码语言:javascript
复制
#docker login `repository url` -u `username` -p `password` 

然后尝试手动获取以下内容:

代码语言:javascript
复制
#docker pull `imagename`
票数 0
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/70548775

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档