keadm init shows success, but the cloudcore process cannot be found

[Watle-fan]

What happened and what you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version):
• KubeEdge version(e.g. cloudcore --version and edgecore --version):

keadm init shows success, but the cloudcore process cannot be found, and the corresponding file is not generated in the corresponding /etc/kubeedge folder. I used isuald instead of docker. Will this replacement container affect keadm init? Modify the relevant configuration files so that keadm init can initialize successfully? kubernets version: 1.24, kubeedge version: 1.15, isulad version: 2.1.5

Before executing the above keadm init command, I have executed the following command for taint tolerance. I uploaded the kubeedge-v1.15.0-linux-amd64.tar.gz and checksum_kubeedge-v1.15.0-linux-amd64.tar.gz.txt files in the etc/kubeedge/ directory, but after executing the keadm init command, the above problem occurred, and there are no task files in the etc/kubeedge/ folder, including the files I uploaded myself.

kubectl describe nodes cloud | grep Taints
kubectl taint nodes cloud node-role.kubernetes.io/control-plane:NoSchedule-

[thinkeng]

kubectl get pod -n kubeedge

[Watle-fan]

kubectl get pod -n kubeedge

After I reset and re-executed it, there was a cloudcore process, but there was still no cloudcore.service under etc/kubeedge, and the uploaded compressed package was gone.

[wbc6080]

Do you want to view cloudcore logs? Because cloudcore has two methods: binary deployment and keadm deployment. Binary deployment can check the log through cloudcore.service, but keadm deployment deploys cloudcore in the form of pod. You can refer to https://kubeedge.io/docs/faq/setup#how-to-check-cloudcore-logs

[Watle-fan]

Do you want to view cloudcore logs? Because cloudcore has two methods: binary deployment and keadm deployment. Binary deployment can check the log through cloudcore.service, but keadm deployment deploys cloudcore in the form of pod. You can refer to https://kubeedge.io/docs/faq/setup#how-to-check-cloudcore-logs
However, my logs still show some errors：

[Shelley-BaoYue]

using v1.15.2 but not v1.15.0 to fix the error log

[Watle-fan]

This issue has been resolved, mainly because since v1.10, CloudCore is running in container mode instead of process mode, and you can see the CloudCore image by looking at docker images。