登录 注册
开源 企业版 高校版 私有云 Gitee AI NEW
开源项目 > 服务器应用 > 容器/虚拟机 &&
扫描微信二维码支付
取消
支付完成
Watch
不关注 关注所有动态 仅关注版本发行动态 关注但不提醒动态
86 Star 471 Fork 273

GVPopenEuler / iSulad

代码 Issues 29 Pull Requests 9 Wiki 统计 流水线
服务
Issues
 / 详情

华为云ecs+isula+k8s kubelet node not found

已完成
缺陷
weixiewen
创建于  
2022-02-15 16:30

【标题描述】
华为云ecs : 2vCPUs | 4 GiB | c6s.large.2
Mirror : openEuler 20.03 64bit
私 192.168.0.70 公 119.3.218.206

isula版本

[root@master ~]# isula version
Client:
Version: 2.0.0
Git commit: 5bf7c66ad4f7095156e87ca455da016f57c3e60f
Built: 2020-03-23T20:55:07.606979235+00:00

Server:
Version: 2.0.0
Git commit: 5bf7c66ad4f7095156e87ca455da016f57c3e60f
Built: 2020-03-23T20:55:07.606979235+00:00

OCI config:
Version: 1.0.1
Default file: /etc/default/isulad/config.json

当前镜像

[root@master ~]# isula images
REPOSITORY TAG IMAGE ID CREATED SIZE
registry.aliyuncs.com/google_containers/kube-proxy v1.20.2 43154ddb57a8 2021-01-13 21:41:03 114.778 MB
registry.aliyuncs.com/google_containers/kube-apiserver v1.20.2 a8c2fdb8bf76 2021-01-13 21:40:56 117.221 MB
registry.aliyuncs.com/google_containers/kube-controller-manager v1.20.2 a27166429d98 2021-01-13 21:40:56 111.674 MB
registry.aliyuncs.com/google_containers/kube-scheduler v1.20.2 ed2c44fbdd78 2021-01-13 21:40:55 45.424 MB
registry.aliyuncs.com/google_containers/etcd 3.4.13-0 0369cf4303ff 2020-08-27 21:47:36 242.862 MB
registry.aliyuncs.com/google_containers/coredns 1.7.0 bfe3a36ebd25 2020-06-18 08:55:59 43.255 MB
registry.aliyuncs.com/google_containers/pause 3.2 80d28bedfe5d 2020-02-14 10:51:50 669.755 KB
pause-amd64 3.0 99e59f495ffa 2016-05-04 14:26:41 735.278 KB

kubelet 日志信息

systemctl status kubelet
Feb 15 13:00:01 master kubelet[27874]: E0215 13:00:01.642142 27874 kubelet.go:2243] node "master" not found
Feb 15 13:00:01 master kubelet[27874]: E0215 13:00:01.742243 27874 kubelet.go:2243] node "master" not found
Feb 15 13:00:01 master kubelet[27874]: E0215 13:00:01.750561 27874 remote_runtime.go:116] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = Failed to pull sandbox
image pause-amd64:3.0: Failed to call pull image
Feb 15 13:00:01 master kubelet[27874]: E0215 13:00:01.750592 27874 kuberuntime_sandbox.go:70] CreatePodSandbox for pod "etcd-master_kube-system(e38423d700b602d3c955ead4c3956414)" failed: rpc error: code = Unknown desc = Failed to pull sandbox image pause-amd64:3.0:
Feb 15 13:00:01 master kubelet[27874]: E0215 13:00:01.750605 27874 kuberuntime_manager.go:755] createPodSandbox for pod "etcd-master_kube-system(e38423d700b602d3c955ead4c3956414)" failed: r>
Feb 15 13:00:01 master kubelet[27874]: E0215 13:00:01.750643 27874 pod_workers.go:191] Error syncing pod e38423d700b602d3c955ead4c3956414 ("etcd-master_kube-system(e38423d700b602d3c955ead4c>
Feb 15 13:00:01 master kubelet[27874]: E0215 13:00:01.842341 27874 kubelet.go:2243] node "master" not found
Feb 15 13:00:01 master kubelet[27874]: E0215 13:00:01.867728 27874 eviction_manager.go:260] eviction manager: failed to get summary stats: failed to get node info: node "master" not found

节点初始化命令

kubeadm init --apiserver-advertise-address=192.168.0.70 --service-cidr=10.96.0.0/12 --image-repository registry.aliyuncs.com/google_containers --kubernetes-version v1.20.2 --pod-network-cidr=10.24.0.0/16 --cri-socket=/var/run/isulad.sock

isula 装载镜像 pause-amd64:3.0后报错
输入图片说明

输入图片说明

尝试docker

kubeadm reset
yum install docker
kubeadm init --apiserver-advertise-address=192.168.0.70 --service-cidr=10.96.0.0/12 --image-repository registry.aliyuncs.com/google_containers --kubernetes-version v1.20.2 --pod-network-cidr=10.24.0.0/16

成功初始化，尚未装网络插件
输入图片说明

问题

Q1：isula无法直接pull pause-amd64:3.0

后尝试通过docker pull save 再load

Q2:master单节点无法初始化

评论 (16)

weixiewen 创建了缺陷

Hi weixiewen, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: iSulad, and any of the maintainers: @haomintsai , @lifeng_isula , @haozi007 , @jingxiaolu

5329419 openeuler ci bot 1632792936
openeuler-ci-bot 添加了
 
sig/iSulad
标签

能把isulad的报错日志拿一下吗？
而且你的这个版本是不是太老了，之前isulad pull镜像的错误修复了好几个；建议升级新的20-03-LTS-SP3版本isulad的版本 为2.0.10

isula日志在哪啊
我先升级下isula，华为云上带的源装的就这版本

升2.0.10报错 
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- An ExecStart= process belonging to unit kubelet.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 255.
Feb 15 17:22:40 master systemd[1]: kubelet.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit kubelet.service has entered the 'failed' state with result 'exit-code'.
Feb 15 17:22:40 master audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=kubelet comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=faile>
Feb 15 17:22:41 master systemd[1]: isulad.service: Start request repeated too quickly.
Feb 15 17:22:41 master systemd[1]: isulad.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit isulad.service has entered the 'failed' state with result 'exit-code'.
Feb 15 17:22:41 master systemd[1]: Failed to start iSulad Application Container Engine.
-- Subject: A start job for unit isulad.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit isulad.service has finished with a failure.
-- 
-- The job identifier is 980 and the job result is failed.
Feb 15 17:22:41 master [7464]: [systemctl start isulad] return code=[1], execute failed by [root(uid=0)] from [pts/0 (121.36.59.153)]
Feb 15 17:22:46 master systemd[1]: isulad.service: Start request repeated too quickly.
Feb 15 17:22:46 master systemd[1]: isulad.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit isulad.service has entered the 'failed' state with result 'exit-code'.
Feb 15 17:22:46 master systemd[1]: Failed to start iSulad Application Container Engine.
-- Subject: A start job for unit isulad.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit isulad.service has finished with a failure.
-- 
-- The job identifier is 1035 and the job result is failed.
Feb 15 17:22:46 master [7478]: [systemctl restart isulad] return code=[1], execute failed by [root(uid=0)] from [pts/0 (121.36.59.153)]

新的一台ecs 自带repo装的

everything                                                                                                                                                      190 kB/s | 9.1 MB     00:48    
EPOL                                                                                                                                                            163 kB/s | 911 kB     00:05    
debuginfo                                                                                                                                                       164 kB/s | 2.8 MB     00:17    
source                                                                                                                                                          190 kB/s | 816 kB     00:04    
Metadata cache created.
[root@ecs-8960 ~]# yum install iSulad
Last metadata expiration check: 0:00:07 ago on Tue 15 Feb 2022 05:37:52 PM CST.
Dependencies resolved.
================================================================================================================================================================================================
 Package                                        Architecture                         Version                                                             Repository                        Size
================================================================================================================================================================================================
Installing:
 iSulad                                         x86_64                               2.0.0-20200321.032232.gitaec8336d.oe1

isula 2.0.5 openEuler 20.09 问题+1
[root@euler ~]# isula version
Client:
  Version:      2.0.5
  Git commit:   f84000843bf2ba98adea547721b235e3b77168e1
  Built:        2020-09-27T17:45:13.009126010+00:00

Server:
  Version:      2.0.5
  Git commit:   f84000843bf2ba98adea547721b235e3b77168e1
  Built:        2020-09-27T17:45:13.009126010+00:00

OCI config:
  Version:      1.0.1
  Default file: /etc/default/isulad/config.json
```![输入图片说明](https://images.gitee.com/uploads/images/2022/0215/235321_885e868f_8657605.png "屏幕截图.png")

没有SP3的源吗？

看一下/etc/isulad/daemon.json的配置

  • 如果log-driver是file，默认在/var/lib/isulad/isulad.log
  • 否则直接看journalctl -u isulad

尝试新版isulad 2.0.9
依旧不能自行pull
isula pull pause-amd64:3.0
Image "pause-amd64:3.0" pulling
Failed to pull image pause-amd64:3.0 with error: Invalid image name, no host found

{
    "group": "isula",
    "default-runtime": "lcr",
    "graph": "/var/lib/isulad",
    "state": "/var/run/isulad",
    "engine": "lcr",
    "log-level": "ERROR",
    "pidfile": "/var/run/isulad.pid",
    "log-opts": {
        "log-file-mode": "0600",
        "log-path": "/var/lib/isulad",
        "max-file": "1",
        "max-size": "30KB"
    },
    "log-driver": "stdout",
    "container-log": {
        "driver": "json-file"
    },
    "hook-spec": "/etc/default/isulad/hooks/default.json",
    "start-timeout": "2m",
    "storage-driver": "overlay2",
    "storage-opts": [
        "overlay2.override_kernel_check=true"
    ],
    "registry-mirrors": [
    "https://xxxxx.mirror.aliyuncs.com"
    ],
    "insecure-registries": [
    ],
    "pod-sandbox-image": "",
    "native.umask": "secure",
    "network-plugin": "",
    "cni-bin-dir": "",
    "cni-conf-dir": "",
    "image-layer-check": false,
    "use-decrypted-key": true,
    "insecure-skip-verify-enforce": false
}

isulad log

2月 16 23:03:01 euler isulad[2148]:           iSula 20220216150301.581 ERROR    /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/entry/connect/grpc/runtime_runtime_service.cc:RunPodSandbox:286 - Object: CRI, Type: Failed to run pod:Failed to pull sandbox image pause-amd64:3.0: Failed to pull image pause-amd64:3.0 with error: Invalid image name, no host found
2月 16 23:03:02 euler isulad[2148]:           iSula 20220216150302.580 - Event: {Object: CRI, Type: Running Pod}
2月 16 23:03:02 euler isulad[2148]:           iSula 20220216150302.580 ERROR    /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/image/oci/storage/image_store/image_store.c:image_store_exists:1571 - Image pause-amd64:3.0 not known
2月 16 23:03:02 euler isulad[2148]:           iSula 20220216150302.580 ERROR    /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/image/image.c:im_image_summary:2002 - No such image:pause-amd64:3.0
2月 16 23:03:02 euler isulad[2148]:           iSula 20220216150302.580 - Event: {Object: pause-amd64:3.0, Type: Pulling}
2月 16 23:03:02 euler isulad[2148]:           iSula 20220216150302.580 ERROR    /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/image/oci/oci_pull.c:pull_image:135 - Invalid image name pause-amd64:3.0, no host found
2月 16 23:03:02 euler isulad[2148]:           iSula 20220216150302.580 ERROR    /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/image/oci/oci_pull.c:oci_do_pull_image:186 - pull image pause-amd64:3.0 failed
2月 16 23:03:02 euler isulad[2148]:           iSula 20220216150302.580 ERROR    /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/image/image.c:im_pull_image:946 - Pull image pause-amd64:3.0 failed
2月 16 23:03:02 euler isulad[2148]:           iSula 20220216150302.580 ERROR    /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/entry/cri/cri_pod_sandbox_manager_service_impl.cc:RunPodSandbox:487 - Failed to pull sandbox image pause-amd64:3.0: Failed to pull image pause-amd64:3.0 with error: Invalid image name, no host found
2月 16 23:03:02 euler isulad[2148]:           iSula 20220216150302.580 ERROR    /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/entry/connect/grpc/runtime_runtime_service.cc:RunPodSandbox:286 - Object: CRI, Type: Failed to run pod:Failed to pull sandbox image pause-amd64:3.0: Failed to pull image pause-amd64:3.0 with error: Invalid image name, no host found

导入pause-amd64后 master起了
低版本 .0是起不来的 是什么原因造成的呢

pull 必须加前缀 docker.io么 为啥呢

"pod-sandbox-image": "改成阿里的pause镜像的完整路径",
否则会去google的仓库下载

registry.aliyuncs.com/google_containers/pause:3.2

嗯 已经成功下了，但还是尚有报错，晚些我再把日志发出

华为云使用20.03sp3 isula 2.0.10报错
输入图片说明

Feb 17 23:15:45 ecs-8960 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 2.
Feb 17 23:15:45 ecs-8960 systemd[1]: Stopped iSulad Application Container Engine.
Feb 17 23:15:45 ecs-8960 systemd[1]: Starting iSulad Application Container Engine...
Feb 17 23:15:45 ecs-8960 isulad[8322]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/lcr/lcr_engine.c:>
Feb 17 23:15:45 ecs-8960 isulad[8322]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/engine.c: new_eng>
Feb 17 23:15:45 ecs-8960 isulad[8322]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/runtime.c: runtime_init: >
Feb 17 23:15:45 ecs-8960 isulad[8322]: Start failed: Failed to init runtime
Feb 17 23:15:45 ecs-8960 systemd[1]: isulad.service: Main process exited, code=exited, status=1/FAILURE
Feb 17 23:15:45 ecs-8960 systemd[1]: isulad.service: Failed with result 'exit-code'.
Feb 17 23:15:45 ecs-8960 systemd[1]: Failed to start iSulad Application Container Engine.
Feb 17 23:15:46 ecs-8960 systemd[1]: isulad.service: Service RestartSec=100ms expired, scheduling restart.
Feb 17 23:15:46 ecs-8960 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 3.
Feb 17 23:15:46 ecs-8960 systemd[1]: Stopped iSulad Application Container Engine.
Feb 17 23:15:46 ecs-8960 systemd[1]: Starting iSulad Application Container Engine...
Feb 17 23:15:46 ecs-8960 isulad[8336]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/lcr/lcr_engine.c:>
Feb 17 23:15:46 ecs-8960 isulad[8336]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/engine.c: new_eng>
Feb 17 23:15:46 ecs-8960 isulad[8336]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/runtime.c: runtime_init: >
Feb 17 23:15:46 ecs-8960 isulad[8336]: Start failed: Failed to init runtime
Feb 17 23:15:46 ecs-8960 systemd[1]: isulad.service: Main process exited, code=exited, status=1/FAILURE
Feb 17 23:15:46 ecs-8960 systemd[1]: isulad.service: Failed with result 'exit-code'.
Feb 17 23:15:46 ecs-8960 systemd[1]: Failed to start iSulad Application Container Engine.
Feb 17 23:15:46 ecs-8960 systemd[1]: isulad.service: Service RestartSec=100ms expired, scheduling restart.
Feb 17 23:15:46 ecs-8960 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 4.
Feb 17 23:15:46 ecs-8960 systemd[1]: Stopped iSulad Application Container Engine.
Feb 17 23:15:46 ecs-8960 systemd[1]: isulad.service: Start request repeated too quickly.
Feb 17 23:15:46 ecs-8960 systemd[1]: isulad.service: Failed with result 'exit-code'.
Feb 17 23:15:46 ecs-8960 systemd[1]: Failed to start iSulad Application Container Engine.
Feb 17 23:17:01 ecs-8960 systemd[1]: Starting iSulad Application Container Engine...
Feb 17 23:17:01 ecs-8960 isulad[8420]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/lcr/lcr_engine.c:>
Feb 17 23:17:01 ecs-8960 isulad[8420]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/engine.c: new_eng>
Feb 17 23:17:01 ecs-8960 isulad[8420]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/runtime.c: runtime_init: >
Feb 17 23:17:01 ecs-8960 isulad[8420]: Start failed: Failed to init runtime
Feb 17 23:17:01 ecs-8960 systemd[1]: isulad.service: Main process exited, code=exited, status=1/FAILURE
Feb 17 23:17:01 ecs-8960 systemd[1]: isulad.service: Failed with result 'exit-code'.
Feb 17 23:17:01 ecs-8960 systemd[1]: Failed to start iSulad Application Container Engine.
Feb 17 23:17:01 ecs-8960 systemd[1]: isulad.service: Service RestartSec=100ms expired, scheduling restart.
Feb 17 23:17:01 ecs-8960 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 1.
Feb 17 23:17:01 ecs-8960 systemd[1]: Stopped iSulad Application Container Engine.
Feb 17 23:17:01 ecs-8960 systemd[1]: Starting iSulad Application Container Engine...
Feb 17 23:17:01 ecs-8960 isulad[8435]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/lcr/lcr_engine.c:>
Feb 17 23:17:01 ecs-8960 isulad[8435]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/engine.c: new_eng>
Feb 17 23:17:01 ecs-8960 isulad[8435]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/runtime.c: runtime_init: >
Feb 17 23:17:01 ecs-8960 isulad[8435]: Start failed: Failed to init runtime
Feb 17 23:17:01 ecs-8960 systemd[1]: isulad.service: Main process exited, code=exited, status=1/FAILURE
Feb 17 23:17:01 ecs-8960 systemd[1]: isulad.service: Failed with result 'exit-code'.
Feb 17 23:17:01 ecs-8960 systemd[1]: Failed to start iSulad Application Container Engine.
Feb 17 23:17:02 ecs-8960 systemd[1]: isulad.service: Service RestartSec=100ms expired, scheduling restart.
Feb 17 23:17:02 ecs-8960 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 2.
Feb 17 23:17:02 ecs-8960 systemd[1]: Stopped iSulad Application Container Engine.
Feb 17 23:17:02 ecs-8960 systemd[1]: Starting iSulad Application Container Engine...
Feb 17 23:17:02 ecs-8960 isulad[8437]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/lcr/lcr_engine.c:>
Feb 17 23:17:02 ecs-8960 isulad[8437]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/engine.c: new_eng>
Feb 17 23:17:02 ecs-8960 isulad[8437]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/runtime.c: runtime_init: >
Feb 17 23:17:02 ecs-8960 isulad[8437]: Start failed: Failed to init runtime
Feb 17 23:17:02 ecs-8960 systemd[1]: isulad.service: Main process exited, code=exited, status=1/FAILURE
Feb 17 23:17:02 ecs-8960 systemd[1]: isulad.service: Failed with result 'exit-code'.
Feb 17 23:17:02 ecs-8960 systemd[1]: Failed to start iSulad Application Container Engine.
Feb 17 23:17:02 ecs-8960 systemd[1]: isulad.service: Service RestartSec=100ms expired, scheduling restart.
Feb 17 23:17:02 ecs-8960 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 3.
Feb 17 23:17:02 ecs-8960 systemd[1]: Stopped iSulad Application Container Engine.
Feb 17 23:17:02 ecs-8960 systemd[1]: isulad.service: Start request repeated too quickly.
Feb 17 23:17:02 ecs-8960 systemd[1]: isulad.service: Failed with result 'exit-code'.
Feb 17 23:17:02 ecs-8960 systemd[1]: Failed to start iSulad Application Container Engine.
Feb 17 23:17:27 ecs-8960 systemd[1]: isulad.service: Start request repeated too quickly.
Feb 17 23:17:27 ecs-8960 systemd[1]: isulad.service: Failed with result 'exit-code'.
Feb 17 23:17:27 ecs-8960 systemd[1]: Failed to start iSulad Application Container Engine.
Feb 17 23:17:48 ecs-8960 systemd[1]: isulad.service: Start request repeated too quickly.
Feb 17 23:17:48 ecs-8960 systemd[1]: isulad.service: Failed with result 'exit-code'.
Feb 17 23:17:48 ecs-8960 systemd[1]: Failed to start iSulad Application Container Engine.
Feb 17 23:19:11 ecs-8960 systemd[1]: Starting iSulad Application Container Engine...
Feb 17 23:19:11 ecs-8960 isulad[8864]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/lcr/lcr_engine.c:>
Feb 17 23:19:11 ecs-8960 isulad[8864]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/engine.c: new_eng>
Feb 17 23:19:11 ecs-8960 isulad[8864]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/runtime.c: runtime_init: >
Feb 17 23:19:11 ecs-8960 isulad[8864]: Start failed: Failed to init runtime
Feb 17 23:19:11 ecs-8960 systemd[1]: isulad.service: Main process exited, code=exited, status=1/FAILURE
Feb 17 23:19:11 ecs-8960 systemd[1]: isulad.service: Failed with result 'exit-code'.
Feb 17 23:19:11 ecs-8960 systemd[1]: Failed to start iSulad Application Container Engine.
Feb 17 23:19:12 ecs-8960 systemd[1]: isulad.service: Service RestartSec=100ms expired, scheduling restart.
Feb 17 23:19:12 ecs-8960 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 1.
Feb 17 23:19:12 ecs-8960 systemd[1]: Stopped iSulad Application Container Engine.
Feb 17 23:19:12 ecs-8960 systemd[1]: Starting iSulad Application Container Engine...
Feb 17 23:19:12 ecs-8960 isulad[8893]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/lcr/lcr_engine.c:>
Feb 17 23:19:12 ecs-8960 isulad[8893]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/engine.c: new_eng>
Feb 17 23:19:12 ecs-8960 isulad[8893]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/runtime.c: runtime_init: >
Feb 17 23:19:12 ecs-8960 isulad[8893]: Start failed: Failed to init runtime
Feb 17 23:19:12 ecs-8960 systemd[1]: isulad.service: Main process exited, code=exited, status=1/FAILURE
Feb 17 23:19:12 ecs-8960 systemd[1]: isulad.service: Failed with result 'exit-code'.
Feb 17 23:19:12 ecs-8960 systemd[1]: Failed to start iSulad Application Container Engine.
Feb 17 23:19:12 ecs-8960 systemd[1]: isulad.service: Service RestartSec=100ms expired, scheduling restart.
Feb 17 23:19:12 ecs-8960 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 2.
Feb 17 23:19:12 ecs-8960 systemd[1]: Stopped iSulad Application Container Engine.
Feb 17 23:19:12 ecs-8960 systemd[1]: Starting iSulad Application Container Engine...
Feb 17 23:19:12 ecs-8960 isulad[8895]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/lcr/lcr_engine.c:>
Feb 17 23:19:12 ecs-8960 isulad[8895]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/engine.c: new_eng>
Feb 17 23:19:12 ecs-8960 isulad[8895]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/runtime.c: runtime_init: >
Feb 17 23:19:12 ecs-8960 isulad[8895]: Start failed: Failed to init runtime
Feb 17 23:19:12 ecs-8960 systemd[1]: isulad.service: Main process exited, code=exited, status=1/FAILURE
Feb 17 23:19:12 ecs-8960 systemd[1]: isulad.service: Failed with result 'exit-code'.
Feb 17 23:19:12 ecs-8960 systemd[1]: Failed to start iSulad Application Container Engine.
Feb 17 23:19:12 ecs-8960 systemd[1]: isulad.service: Service RestartSec=100ms expired, scheduling restart.
Feb 17 23:19:12 ecs-8960 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 3.
Feb 17 23:19:12 ecs-8960 systemd[1]: Stopped iSulad Application Container Engine.
Feb 17 23:19:12 ecs-8960 systemd[1]: Starting iSulad Application Container Engine...
Feb 17 23:19:12 ecs-8960 isulad[8909]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/lcr/lcr_engine.c:>
Feb 17 23:19:12 ecs-8960 isulad[8909]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/engine.c: new_eng>
Feb 17 23:19:12 ecs-8960 isulad[8909]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/runtime.c: runtime_init: >
Feb 17 23:19:12 ecs-8960 isulad[8909]: Start failed: Failed to init runtime
Feb 17 23:19:12 ecs-8960 systemd[1]: isulad.service: Main process exited, code=exited, status=1/FAILURE
Feb 17 23:19:12 ecs-8960 systemd[1]: isulad.service: Failed with result 'exit-code'.
Feb 17 23:19:12 ecs-8960 systemd[1]: Failed to start iSulad Application Container Engine.
Feb 17 23:19:12 ecs-8960 systemd[1]: isulad.service: Service RestartSec=100ms expired, scheduling restart.
Feb 17 23:19:12 ecs-8960 systemd[1]: isulad.service: Scheduled restart job, restart counter is at 4.
Feb 17 23:19:12 ecs-8960 systemd[1]: Stopped iSulad Application Container Engine.
Feb 17 23:19:12 ecs-8960 systemd[1]: isulad.service: Start request repeated too quickly.
Feb 17 23:19:12 ecs-8960 systemd[1]: isulad.service: Failed with result 'exit-code'.
Feb 17 23:19:12 ecs-8960 systemd[1]: Failed to start iSulad Application Container Engine.
Feb 17 23:19:21 ecs-8960 systemd[1]: isulad.service: Start request repeated too quickly.
Feb 17 23:19:21 ecs-8960 systemd[1]: isulad.service: Failed with result 'exit-code'.
Feb 17 23:19:21 ecs-8960 systemd[1]: Failed to start iSulad Application Container Engine.

只有这么多日志吗？

 /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/lcr/lcr_engine.c:>
Feb 17 23:19:12 ecs-8960 isulad[8909]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/engines/engine.c: new_eng>
Feb 17 23:19:12 ecs-8960 isulad[8909]:          isulad /home/abuild/rpmbuild/BUILD/iSulad/src/daemon/modules/runtime/runtime.c: runtime_init: >

看着不完整？后面还有信息才对

5595769 duguhaotian 1605235330
haozi007 通过openeuler/iSulad Pull Request !1332 将任务状态从 待办的 修改为已完成

登录 后才可以发表评论

状态
负责人
标签
sig/iSulad
项目
未立项任务
未立项任务
里程碑
未关联
未关联
Pull Requests
未关联
未关联
关联的 Pull Requests 被合并后可能会关闭此 issue
分支
未关联
分支 (9)
标签 (27)
master
stable-v2.0.x
dev-sandbox
dev-2022
dev-newrest
work
dev-network
shimv2
network
v2.1.5
v2.1.4
v2.1.3
v2.1.2
v2.1.1
v2.0.18
v2.0.17
v2.0.16
v2.0.15
v2.0.14
v2.0.13
v2.0.12
v2.0.11
v2.1.0
v2.0.10
v2.0.9
v2.1.0-alpha
v2.0.8
v2.0.7
v2.0.6
v2.0.5
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v2.0.1-alpha
v2.0.0
开始日期   -   截止日期
-
置顶选项
不置顶
置顶等级：高
置顶等级：中
置顶等级：低
优先级
不指定
严重
主要
次要
不重要
预计工期 （小时）
参与者（3）
5329419 openeuler ci bot 1632792936 5595769 duguhaotian 1605235330
C
1
https://gitee.com/openeuler/iSulad.git
git@gitee.com:openeuler/iSulad.git
openeuler
iSulad
iSulad
点此查找更多帮助

搜索帮助

Git 命令在线学习 如何在 Gitee 导入 GitHub 仓库
Git 仓库基础操作
企业版和社区版功能对比
SSH 公钥设置
如何处理代码冲突
仓库体积过大，如何减小？
如何找回被删除的仓库数据
Gitee 产品配额说明
GitHub仓库快速导入Gitee及同步更新
什么是 Release（发行版）
将 PHP 项目自动发布到 packagist.org
仓库举报
回到顶部
53164aa7 5694891 3bd8fe86 5694891