麒麟kylin linux v10部署k3s,pod启动失败,哪位大神帮忙看一下

环境信息:
K3s 版本: v1.30.14+k3s1

节点 CPU 架构、操作系统和版本:: Linux localhost.localdomain 4.19.90-52.22.v2207.ky10.aarch64 #1 SMP Tue Mar 14 11:52:45 CST 2023 aarch64 aarch64 aarch64 GNU/Linux

集群配置:1 servers

问题描述:

麒麟kylin linux v10部署k3s,pod启动失败


复现步骤:

预期结果:
pod正常运行

实际结果:
pod启动失败

附加上下文/日志:

日志
[root@localhost ~]# kubectl -nkube-system get pod
NAME                                     READY   STATUS             RESTARTS     AGE
coredns-67bcbdcb6c-6mcfm                 0/1     CrashLoopBackOff   1 (2s ago)   9s
local-path-provisioner-84c7c7f76-r8jtd   0/1     CrashLoopBackOff   1 (3s ago)   9s
metrics-server-697878cfd8-gjb7f          0/1     CrashLoopBackOff   1 (3s ago)   9s
[root@localhost ~]# kubectl -nkube-system describe pod coredns-67bcbdcb6c-6mcfm
Name:                 coredns-67bcbdcb6c-6mcfm
Namespace:            kube-system
Priority:             2000000000
Priority Class Name:  system-cluster-critical
Service Account:      coredns
Node:                 localhost.localdomain/10.7.47.9
Start Time:           Fri, 07 Nov 2025 12:05:38 +0800
Labels:               k8s-app=kube-dns
                      pod-template-hash=67bcbdcb6c
Annotations:          <none>
Status:               Running
IP:                   
IPs:                  <none>
Controlled By:        ReplicaSet/coredns-67bcbdcb6c
Containers:
  coredns:
    Container ID:  containerd://d299fc53c2396121184d1205f4a814985acd88ad57b4b6302cbdc3f74c4c8bdf
    Image:         registry.maxelms.com:5001/rancher/mirrored-coredns-coredns:1.12.1
    Image ID:      registry.maxelms.com:5001/rancher/mirrored-coredns-coredns@sha256:4f7a57135719628cf2070c5e3cbde64b013e90d4c560c5ecbf14004181f91998
    Ports:         53/UDP, 53/TCP, 9153/TCP
    Host Ports:    0/UDP, 0/TCP, 0/TCP
    Args:
      -conf
      /etc/coredns/Corefile
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       StartError
      Message:      failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: can't get final child's PID from pipe: EOF: unknown
      Exit Code:    128
      Started:      Thu, 01 Jan 1970 08:00:00 +0800
      Finished:     Fri, 07 Nov 2025 12:05:45 +0800
    Ready:          False
    Restart Count:  1
    Limits:
      memory:  170Mi
    Requests:
      cpu:        100m
      memory:     70Mi
    Liveness:     http-get http://:8080/health delay=60s timeout=1s period=10s #success=1 #failure=3
    Readiness:    http-get http://:8181/ready delay=0s timeout=1s period=2s #success=1 #failure=3
    Environment:  <none>
    Mounts:
      /etc/coredns from config-volume (ro)
      /etc/coredns/custom from custom-config-volume (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-dpk8k (ro)
Conditions:
  Type                        Status
  PodReadyToStartContainers   False 
  Initialized                 True 
  Ready                       False 
  ContainersReady             False 
  PodScheduled                True 
Volumes:
  config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      coredns
    Optional:  false
  custom-config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      coredns-custom
    Optional:  true
  kube-api-access-dpk8k:
    Type:                     Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:   3607
    ConfigMapName:            kube-root-ca.crt
    ConfigMapOptional:        <nil>
    DownwardAPI:              true
QoS Class:                    Burstable
Node-Selectors:               kubernetes.io/os=linux
Tolerations:                  CriticalAddonsOnly op=Exists
                              node-role.kubernetes.io/control-plane:NoSchedule op=Exists
                              node-role.kubernetes.io/master:NoSchedule op=Exists
                              node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                              node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Topology Spread Constraints:  kubernetes.io/hostname:DoNotSchedule when max skew 1 is exceeded for selector k8s-app=kube-dns
                              topology.kubernetes.io/zone:ScheduleAnyway when max skew 1 is exceeded for selector k8s-app=kube-dns
Events:
  Type     Reason          Age                From               Message
  ----     ------          ----               ----               -------
  Normal   Scheduled       16s                default-scheduler  Successfully assigned kube-system/coredns-67bcbdcb6c-6mcfm to localhost.localdomain
  Normal   Pulling         15s                kubelet            Pulling image "registry.maxelms.com:5001/rancher/mirrored-coredns-coredns:1.12.1"
  Normal   Pulled          12s                kubelet            Successfully pulled image "registry.maxelms.com:5001/rancher/mirrored-coredns-coredns:1.12.1" in 2.915s (2.915s including waiting). Image size: 22382796 bytes.
  Warning  Failed          12s                kubelet            Error: failed to get sandbox container task: no running task found: task 30b7a706bf6c87de42e86f3cacb26e454b0cce1c00888cd5229746388277f173 not found: not found
  Normal   Pulled          10s (x2 over 11s)  kubelet            Container image "registry.maxelms.com:5001/rancher/mirrored-coredns-coredns:1.12.1" already present on machine
  Normal   Created         10s (x2 over 11s)  kubelet            Created container: coredns
  Warning  Failed          9s (x2 over 10s)   kubelet            Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: can't get final child's PID from pipe: EOF: unknown
  Normal   SandboxChanged  3s (x9 over 11s)   kubelet            Pod sandbox changed, it will be killed and re-created.
  Warning  BackOff         2s (x7 over 9s)    kubelet            Back-off restarting failed container coredns in pod coredns-67bcbdcb6c-6mcfm_kube-system(5c6ae443-efea-440b-b6c7-090809d3ee0a)

问题解决,两个步骤
一、麒麟v10系统有自带的podman,需要先卸载podman,不然会和containerd有冲突导致容器无法创建
二、卸载podman后发现容器启动还是会失败,并报错


排查后发现镜像使用了amd架构的,把镜像换成arm架构后问题解决,pod也启动成功

1 个赞