kubeedge-pi-counter-784d57c5d4-d7tw7 0/1 ContainerCreating

what happended: I'm trying to use kubeedge-counter-demo to test device control ,however when I follow the guideline in the webpage to create the counter device the status of its pod remain ContainerCreating

problem description:


[root@cloud-master1 crds]# kubectl get node
NAME              STATUS     ROLES        AGE   VERSION
cloud-master1     Ready      master       47h   v1.18.0
edge-mini-1       Ready      agent,edge   42h   v1.19.3-kubeedge-v1.7.0
edge-rasperry-1   Ready      agent,edge   42h   v1.19.3-kubeedge-v1.7.0
edge-zy           NotReady   agent,edge   24h   v1.19.3-kubeedge-v1.7.0
node              Ready      agent,edge   43h   v1.19.3-kubeedge-v1.7.0
[root@cloud-master1 crds]# 
[root@cloud-master1 crds]# 
[root@cloud-master1 crds]# kubectl get device
NAME      AGE
counter   47m
[root@cloud-master1 crds]# kubectl describe device -oyaml
Error: unknown shorthand flag: 'o' in -oyaml
See 'kubectl describe --help' for usage.
[root@cloud-master1 crds]# kubectl get  device counter -oyaml
apiVersion: devices.kubeedge.io/v1alpha2
kind: Device
metadata:
creationTimestamp: "2021-11-03T02:21:22Z"
generation: 2
labels:
description: counter
managedFields:
- apiVersion: devices.kubeedge.io/v1alpha2
fieldsType: FieldsV1
fieldsV1:
  f:metadata:
    f:labels:
      .: {}
      f:description: {}
  f:spec:
    .: {}
    f:deviceModelRef:
      .: {}
      f:name: {}
    f:nodeSelector:
      .: {}
      f:nodeSelectorTerms: {}
  f:status: {}
manager: kubectl
operation: Update
time: "2021-11-03T02:21:22Z"
- apiVersion: devices.kubeedge.io/v1alpha2
fieldsType: FieldsV1
fieldsV1:
  f:status:
    f:twins: {}
manager: Go-http-client
operation: Update
time: "2021-11-03T02:25:03Z"
name: counter
namespace: default
resourceVersion: "632970"
selfLink: /apis/devices.kubeedge.io/v1alpha2/namespaces/default/devices/counter
uid: 89e1122d-0abe-4e78-b35b-cf69e429e3bf
spec:
deviceModelRef:
name: counter-model
nodeSelector:
nodeSelectorTerms:
- matchExpressions:
  - key: ""
    operator: In
    values:
    - edge-rasperry-1
status:
twins:
- desired:
  metadata:
    timestamp: "1635"
    type: string
  value: "ON"
propertyName: status
reported:
  metadata:
    timestamp: "1635"
    type: string
  value: "1"
[root@cloud-master1 crds]#

NAME READY STATUS RESTARTS AGE kubeedge-counter-app-6984dcb4dd-4jdk6 1/1 Running 0 47m kubeedge-pi-counter-784d57c5d4-d7tw7 0/1 ContainerCreating 0 47m

[root@cloud-master1 crds]# kubectl get pod kubeedge-pi-counter-784d57c5d4-d7tw7 -oyaml apiVersion: v1 kind: Pod metadata: creationTimestamp: "2021-11-03T02:22:58Z" generateName: kubeedge-pi-counter-784d57c5d4- labels: k8s-app: kubeedge-pi-counter pod-template-hash: 784d57c5d4 managedFields:

apiVersion: v1 fieldsType: FieldsV1 fieldsV1: f:metadata: f:generateName: {} f:labels: .: {} f:k8s-app: {} f:pod-template-hash: {} f:ownerReferences: .: {} k:{"uid":"6f93650e-ce75-4e7c-88f4-d2e89711ca30"}: .: {} f:apiVersion: {} f:blockOwnerDeletion: {} f:controller: {} f:kind: {} f:name: {} f:uid: {} f:spec: f:containers: k:{"name":"kubeedge-pi-counter"}: .: {} f:image: {} f:imagePullPolicy: {} f:name: {} f:resources: {} f:terminationMessagePath: {} f:terminationMessagePolicy: {} f:dnsPolicy: {} f:enableServiceLinks: {} f:hostNetwork: {} f:nodeSelector: .: {} f:node-role.kubernetes.io/edge: {} f:restartPolicy: {} f:schedulerName: {} f:securityContext: {} f:terminationGracePeriodSeconds: {} manager: kube-controller-manager operation: Update time: "2021-11-03T02:22:58Z"
apiVersion: v1 fieldsType: FieldsV1 fieldsV1: f:status: f:conditions: .: {} k:{"type":"PodScheduled"}: .: {} f:lastProbeTime: {} f:message: {} f:reason: {} f:status: {} f:type: {} manager: kube-scheduler operation: Update time: "2021-11-03T02:22:58Z"
apiVersion: v1 fieldsType: FieldsV1 fieldsV1: f:status: f:conditions: k:{"type":"Initialized"}: .: {} f:lastProbeTime: {} f:lastTransitionTime: {} f:status: {} f:type: {} k:{"type":"PodScheduled"}: f:lastTransitionTime: {} k:{"type":"Ready"}: .: {} f:lastProbeTime: {} f:lastTransitionTime: {} f:message: {} f:reason: {} f:status: {} f:type: {} f:containerStatuses: {} f:hostIP: {} f:podIP: {} f:podIPs: .: {} k:{"ip":"192.168.1.40"}: .: {} f:ip: {} f:startTime: {} manager: cloudcore operation: Update time: "2021-11-03T02:24:38Z" name: kubeedge-pi-counter-784d57c5d4-d7tw7 namespace: default ownerReferences:
apiVersion: apps/v1 blockOwnerDeletion: true controller: true kind: ReplicaSet name: kubeedge-pi-counter-784d57c5d4 uid: 6f93650e-ce75-4e7c-88f4-d2e89711ca30 resourceVersion: "632844" selfLink: /api/v1/namespaces/default/pods/kubeedge-pi-counter-784d57c5d4-d7tw7 uid: f5957fc9-3449-47ad-b743-c19a77ae22e9 spec: containers:
image: kubeedge/kubeedge-pi-counter:v1.0.0 imagePullPolicy: IfNotPresent name: kubeedge-pi-counter resources: {} terminationMessagePath: /dev/termination-log terminationMessagePolicy: File volumeMounts:
- mountPath: /var/run/secrets/kubernetes.io/serviceaccount name: default-token-6wchc readOnly: true dnsPolicy: ClusterFirst enableServiceLinks: true hostNetwork: true nodeName: edge-mini-1 nodeSelector: node-role.kubernetes.io/edge: "" priority: 0 restartPolicy: Always schedulerName: default-scheduler securityContext: {} serviceAccount: default serviceAccountName: default terminationGracePeriodSeconds: 30 tolerations:
effect: NoExecute key: node.kubernetes.io/not-ready operator: Exists tolerationSeconds: 300
effect: NoExecute key: node.kubernetes.io/unreachable operator: Exists tolerationSeconds: 300 volumes:
name: default-token-6wchc secret: defaultMode: 420 secretName: default-token-6wchc status: conditions:
lastProbeTime: null lastTransitionTime: "2021-11-03T02:24:38Z" status: "True" type: Initialized
lastProbeTime: null lastTransitionTime: "2021-11-03T02:24:38Z" message: 'containers with unready status: [kubeedge-pi-counter]' reason: ContainersNotReady status: "False" type: Ready
lastProbeTime: null lastTransitionTime: null status: "True" type: PodScheduled containerStatuses:
image: kubeedge/kubeedge-pi-counter:v1.0.0 imageID: "" lastState: {} name: kubeedge-pi-counter ready: false restartCount: 0 started: false state: waiting: reason: ContainerCreating hostIP: 192.168.1.40 phase: Pending podIP: 192.168.1.40 podIPs:
ip: 192.168.1.40 qosClass: BestEffort startTime: "2021-11-03T02:24:31Z"

[root@cloud-master1 crds]# kubectl describe pod kubeedge-pi-counter-784d57c5d4-d7tw7 Name: kubeedge-pi-counter-784d57c5d4-d7tw7 Namespace: default Priority: 0 Node: edge-mini-1/192.168.1.40 Start Time: Wed, 03 Nov 2021 10:24:31 +0800 Labels: k8s-app=kubeedge-pi-counter pod-template-hash=784d57c5d4 Annotations: Status: Pending IP: 192.168.1.40 IPs: IP: 192.168.1.40 Controlled By: ReplicaSet/kubeedge-pi-counter-784d57c5d4 Containers: kubeedge-pi-counter: Container ID:
Image: kubeedge/kubeedge-pi-counter:v1.0.0 Image ID:
Port: Host Port: State: Waiting Reason: ContainerCreating Ready: False Restart Count: 0 Environment: Mounts: /var/run/secrets/kubernetes.io/serviceaccount from default-token-6wchc (ro) Conditions: Type Status Initialized True Ready False PodScheduled True Volumes: default-token-6wchc: Type: Secret (a volume populated by a Secret) SecretName: default-token-6wchc Optional: false QoS Class: BestEffort Node-Selectors: node-role.kubernetes.io/edge= Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s node.kubernetes.io/unreachable:NoExecute for 300s Events: Type Reason Age From Message

Warning FailedScheduling default-scheduler 0/5 nodes are available: 1 node(s) didn't match node selector, 4 node(s) had taint {node.kubernetes.io/unreachable: }, that the pod didn't tolerate. Warning FailedScheduling default-scheduler 0/5 nodes are available: 1 node(s) didn't match node selector, 4 node(s) had taint {node.kubernetes.io/unreachable: }, that the pod didn't tolerate. Normal Scheduled default-scheduler Successfully assigned default/kubeedge-pi-counter-784d57c5d4-d7tw7 to edge-mini-1

kubeedge / examples

kubeedge-pi-counter-784d57c5d4-d7tw7 0/1 ContainerCreating #108