CentOS 7.6安装 cri-o-1.11.11-1后无法启动，报错：
> systemctl status crio.service -l
● crio.service - Open Container Initiative Daemon
Loaded: loaded (/usr/lib/systemd/system/crio.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2019-07-03 10:17:06 CST; 12s ago
Docs: https://github.com/kubernetes-sigs/cri-o
Process: 21876 ExecStart=/usr/bin/crio $CRIO_STORAGE_OPTIONS $CRIO_NETWORK_OPTIONS (code=exited, status=1/FAILURE)
Main PID: 21876 (code=exited, status=1/FAILURE)
Jul 03 10:17:06 registry systemd[1]: Starting Open Container Initiative Daemon...
Jul 03 10:17:06 registry crio[21876]: time="2019-07-03 10:17:06.691820122+08:00" level=fatal msg="invalid --runtime value "stat /usr/bin/runc: no such file or directory""
Jul 03 10:17:06 registry systemd[1]: crio.service: main process exited, code=exited, status=1/FAILURE
Jul 03 10:17:06 registry systemd[1]: Failed to start Open Container Initiative Daemon.
Jul 03 10:17:06 registry systemd[1]: Unit crio.service entered failed state.
Jul 03 10:17:06 registry systemd[1]: crio.service failed.
原因是 stat /usr/bin/runc: no such file or directory。
通常情况如果我们安装了docker,那runc也安装了，只是没有安装在/usr/bin/runc目录下。
于是我们看下runc安装在哪个目录，并把它软连接到/usr/bin目录下
> which runc
/usr/sbin/runc
> ln -s /usr/sbin/runc /usr/bin/runc
再次启动CRI-O，便启动成功了。
> systemctl start crio
> systemctl status crio.service -l
● crio.service - Open Container Initiative Daemon
Loaded: loaded (/usr/lib/systemd/system/crio.service; disabled; vendor preset: disabled)
Active: active (running) since Wed 2019-07-03 10:38:24 CST; 4s ago
Docs: https://github.com/kubernetes-sigs/cri-o
Main PID: 23960 (crio)
Tasks: 10
Memory: 21.1M
CGroup: /system.slice/crio.service
└─23960 /usr/bin/crio
Jul 03 10:38:24 registry systemd[1]: Starting Open Container Initiative Daemon...
Jul 03 10:38:24 registry systemd[1]: Started Open Container Initiative Daemon.
