Kubernetes1.9.0 kubeadm init - crictl not found in system path
Asked Answered
S

2

10

I am setting up kubernetes cluster on a Centos 7 machine, and the kubeadm init command gives me the below warning message.

[init] Using Kubernetes version: v1.9.0
[init] Using Authorization modes: [Node RBAC]
[preflight] Running pre-flight checks.
        [WARNING SystemVerification]: docker version is greater than the most recently validated version. Docker version: 17.09.1-ce. Max validated version: 17.03
        [WARNING FileExisting-crictl]: crictl not found in system path

How can I fix this crictl not found in system path warning? Do I need to install any additional software?

Samellasameness answered 20/12, 2017 at 14:36 Comment(0)
C
6

Yes, you need additional software. crictl is part of the cri-tools repo on github.

At least when I encountered this problem (Dec 20, 2017), cri-tools isn't available on kubernete's package repo, so I had to download source and build it. cri-tools is written in go, so you may need to install golang on your system as well.

Chuff answered 20/12, 2017 at 17:42 Comment(0)
A
3

I installed crictl with

   go get github.com/kubernetes-incubator/cri-tools/cmd/crictl

If you don have go on your system, you could install crictl from

https://github.com/kubernetes-incubator/cri-tools/releases

Alexandriaalexandrian answered 8/4, 2018 at 7:29 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.