首页 > 其他分享 >k8s - ERROR: image can't be pulled

k8s - ERROR: image can't be pulled

时间:2024-05-06 10:47:41浏览次数:24  
标签:professionals zgrpc mytest image server go k8s pulled

 

 

 

Tested the image:

zzh@ZZHPC:/zdata/Github/zgrpc-go-professionals$ kubectl run mytest --image=zgrpc-go-professionals:server
pod/mytest created
zzh@ZZHPC:/zdata/Github/zgrpc-go-professionals$ kubectl get pods
NAME     READY   STATUS         RESTARTS   AGE
mytest   0/1     ErrImagePull   0          5s

zzh@ZZHPC:/zdata/Github/zgrpc-go-professionals$ kubectl describe pod mytest
Name:             mytest
Namespace:        default
Priority:         0
Service Account:  default
Node:             kind-worker/172.18.0.3
Start Time:       Mon, 06 May 2024 10:33:02 +0800
Labels:           run=mytest
Annotations:      <none>
Status:           Pending
IP:               10.244.2.7
IPs:
  IP:  10.244.2.7
Containers:
  mytest:
    Container ID:   
    Image:          zgrpc-go-professionals:server
    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-5clv9 (ro)
Conditions:
  Type                        Status
  PodReadyToStartContainers   True 
  Initialized                 True 
  Ready                       False 
  ContainersReady             False 
  PodScheduled                True 
Volumes:
  kube-api-access-5clv9:
    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  90s                default-scheduler  Successfully assigned default/mytest to kind-worker
  Warning  Failed     44s (x3 over 89s)  kubelet            Failed to pull image "zgrpc-go-professionals:server": 
failed to pull and unpack image "docker.io/library/zgrpc-go-professionals:server":
failed to resolve reference "docker.io/library/zgrpc-go-professionals:server":
pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed Warning Failed 44s (x3 over 89s) kubelet Error: ErrImagePull Normal BackOff 17s (x4 over 88s) kubelet Back-off pulling image "zgrpc-go-professionals:server" Warning Failed 17s (x4 over 88s) kubelet Error: ImagePullBackOff Normal Pulling 3s (x4 over 91s) kubelet Pulling image "zgrpc-go-professionals:server"

 

标签:professionals,zgrpc,mytest,image,server,go,k8s,pulled
From: https://www.cnblogs.com/zhangzhihui/p/18174454

相关文章

  • WPF Image open ZoomIn ZoomOut reset
    //xaml<Windowx:Class="WpfApp94.MainWindow"xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"xmlns:d="http://schemas.mic......
  • k8s核心组件详解和分层架构
    k8s核心组件master中的核心组件api-server(接口服务,基于rest风格开放k8s接口的服务)kube-controller-manager(管理各个类型的控制器,针对k8s中的各种资源进行管理)cloud-controller-manager(云控制管理器,第三方云平台提供的控制器,api对接管理功能)kube-scheduler(调度器,负责将po......
  • kind部署k8s集群和kube-ovn
    #docker容器作为k8snode,容器里面通过containerd拉起Pod。cat<<EOF|kindcreatecluster--namekube-ovn--config-kind:ClusterapiVersion:kind.x-k8s.io/v1alpha4networking:kubeProxyMode:ipvsdisableDefaultCNI:trueipFamily:ipv4apiServerAddress......
  • K8S 创建Spring-boot项目并进行项目启动与访问
     ##Spring-boot 的helloworld项目packagecom.example.demo;importjava.time.LocalDateTime;importjava.time.format.DateTimeFormatter;importorg.springframework.web.bind.annotation.GetMapping;importorg.springframework.web.bind.annotation.RequestMappi......
  • Kubernetes源码二次开发系列(一到三),玩转高阶K8s开发
    Kubernetes源码二次开发通常涉及以下步骤:环境准备:安装和配置Go环境,确保Go版本与Kubernetes项目兼容。获取源码:从GitHub克隆Kubernetes仓库到本地。设置工作环境:通过make命令设置编译环境。修改源码:根据需求修改Kubernetes源码。编译:使用makeall编译所有组......
  • BufferedImage内存泄漏和溢出问题
    java的ImageIO处理图片在使用Thumbnailator时出现了OOM问题,但是其使用方法只有一行代码,无法针对其内部使用的对象进行资源释放,所以使用原生的Java类库中ImageIO来处理图片。关键有三个类:ImageIO、BufferedImage、GraphicsImageIO类包含两个静态方法:read()和write(),通过这两......
  • 最小化安装 MSVC ( 可用于 graalvm native-image )
    前言自从接触了native-image,就想把所有Java项目全用native-image编译一遍,谁不喜欢exe呢......
  • kubernetes(k8s)
    应用程序部署的演变过程在部署应用程序的方式上,主要经历了三个时代传统部署互联网早期,会直接将应用程序部署在物理机上优点:简单,不需要其他技术的参与缺点:不能为应用程序定义资源使用边界,很难合理的分配计算资源,而且程序之间容易产生影响虚拟化部署可以在一台物理......
  • Apache SeaTunnel k8s 集群模式 Zeta 引擎部署指南
    SeaTunnel提供了一种运行Zeta引擎(cluster-mode)的方法,可以让Kubernetes在本地运行Zeta引擎,实现更高效的应用程序部署和管理。在本文中,我们将探索SeaTunnelk8s运行zeta引擎(cluster-mode模式)的更多信息,了解如何更好地利用Zeta引擎的优势。将SeaTunnel上传至服务器上。我之前......
  • k8s的Service详解
    一、Service基本了解Service存在的意义?引入Service主要是解决Pod的动态变化,通过创建Service,可以为一组具有相同功能的容器应用提供一个统一的入口地址,并且将请求负载分发到后端的各个容器应用上。若提供服务的容器应用是分布式,所以存在多个pod副本,而Pod副本......