Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unsupported container runtime: cri-o #2467

Open
Nello-Angelo opened this issue Dec 2, 2024 · 3 comments
Open

Unsupported container runtime: cri-o #2467

Nello-Angelo opened this issue Dec 2, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@Nello-Angelo
Copy link

What is version of KubeKey has the issue?

3.1.7

What is your os environment?

debian 11.6

KubeKey config file

apiVersion: kubekey.kubesphere.io/v1alpha2
kind: Cluster
metadata:
  name: sample
spec:
  hosts:
    - {
        name: master,
        address: 192.168.163.135,
        internalAddress: 192.168.163.135,
        user: root,
        password: "123",
      }
  roleGroups:
    etcd:
      - master
    control-plane:
      - master
    worker:
      - master
  controlPlaneEndpoint:
    internalLoadbalancer: haproxy
    domain: lb.kubesphere.local
    address: ""
    port: 6443
  kubernetes:
    version: v1.31.2
    clusterName: cluster.local
    masqueradeAll: false
    maxPods: 110
    nodeCidrMaskSize: 24
    proxyMode: ipvs
    autoRenewCerts: true
    containerManager: cri-o
  etcd:
    type: kubeadm
  network:
    plugin: calico
    calico:
      ipipMode: Never
      vxlanMode: Never
      vethMTU: 1440
    kubePodsCIDR: 10.233.64.0/18
    kubeServiceCIDR: 10.233.0.0/18
    multusCNI:
      enabled: false

A clear and concise description of what happend.

Unsupported container runtime: cri-o

Relevant log output

root@debian:~# ./kk create cluster -f config.yaml


 _   __      _          _   __
| | / /     | |        | | / /
| |/ / _   _| |__   ___| |/ /  ___ _   _
|    \| | | | '_ \ / _ \    \ / _ \ | | |
| |\  \ |_| | |_) |  __/ |\  \  __/ |_| |
\_| \_/\__,_|_.__/ \___\_| \_/\___|\__, |
                                    __/ |
                                   |___/

02:29:07 MSK [GreetingsModule] Greetings
02:29:07 MSK message: [master]
Greetings, KubeKey!
02:29:07 MSK success: [master]
02:29:07 MSK [NodePreCheckModule] A pre-check on nodes
02:29:07 MSK success: [master]
02:29:07 MSK [ConfirmModule] Display confirmation form
+--------+------+------+---------+----------+-------+-------+---------+-----------+--------+--------+------------+------------+-------------+------------------+--------------+
| name   | sudo | curl | openssl | ebtables | socat | ipset | ipvsadm | conntrack | chrony | docker | containerd | nfs client | ceph client | glusterfs client | time         |
+--------+------+------+---------+----------+-------+-------+---------+-----------+--------+--------+------------+------------+-------------+------------------+--------------+
| master | y    | y    | y       | y        | y     | y     |         | y         |        |        |            |            |             |                  | MSK 02:29:07 |
+--------+------+------+---------+----------+-------+-------+---------+-----------+--------+--------+------------+------------+-------------+------------------+--------------+

This is a simple check of your environment.
Before installation, ensure that your machines meet all requirements specified at
https://github.com/kubesphere/kubekey#requirements-and-recommendations

Install k8s with specify version:  v1.31.2

Continue this installation? [yes/no]: yes
02:29:10 MSK success: [LocalHost]
02:29:10 MSK [NodeBinariesModule] Download installation binaries
02:29:10 MSK message: [localhost]
downloading amd64 kubeadm v1.31.2 ...
02:29:11 MSK message: [localhost]
kubeadm exists
02:29:11 MSK message: [localhost]
downloading amd64 kubelet v1.31.2 ...
02:29:12 MSK message: [localhost]
kubelet exists
02:29:12 MSK message: [localhost]
downloading amd64 kubectl v1.31.2 ...
02:29:12 MSK message: [localhost]
kubectl exists
02:29:12 MSK message: [localhost]
downloading amd64 helm v3.14.3 ...
02:29:13 MSK message: [localhost]
helm exists
02:29:13 MSK message: [localhost]
downloading amd64 kubecni v1.2.0 ...
02:29:13 MSK message: [localhost]
kubecni exists
02:29:13 MSK message: [localhost]
downloading amd64 crictl v1.29.0 ...
02:29:13 MSK message: [localhost]
crictl exists
02:29:13 MSK message: [localhost]
downloading amd64 etcd v3.5.13 ...
02:29:14 MSK message: [localhost]
etcd exists
02:29:14 MSK message: [localhost]
downloading amd64 calicoctl v3.27.4 ...
02:29:14 MSK message: [localhost]
calicoctl exists
02:29:14 MSK success: [LocalHost]
02:29:14 MSK [ConfigureOSModule] Get OS release
02:29:14 MSK success: [master]
02:29:14 MSK [ConfigureOSModule] Prepare to init OS
02:29:15 MSK success: [master]
02:29:15 MSK [ConfigureOSModule] Generate init os script
02:29:15 MSK success: [master]
02:29:15 MSK [ConfigureOSModule] Exec init os script
02:29:15 MSK stdout: [master]
net.ipv4.conf.default.rp_filter = 0
net.ipv4.conf.all.rp_filter = 0
net.ipv4.ip_forward = 1
net.bridge.bridge-nf-call-arptables = 1
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.ip_local_reserved_ports = 30000-32767
net.core.netdev_max_backlog = 65535
net.core.rmem_max = 33554432
net.core.wmem_max = 33554432
net.core.somaxconn = 32768
net.ipv4.tcp_max_syn_backlog = 1048576
net.ipv4.neigh.default.gc_thresh1 = 512
net.ipv4.neigh.default.gc_thresh2 = 2048
net.ipv4.neigh.default.gc_thresh3 = 4096
net.ipv4.tcp_retries2 = 15
net.ipv4.tcp_max_tw_buckets = 1048576
net.ipv4.tcp_max_orphans = 65535
net.ipv4.tcp_keepalive_time = 600
net.ipv4.tcp_keepalive_intvl = 30
net.ipv4.tcp_keepalive_probes = 10
net.ipv4.udp_rmem_min = 131072
net.ipv4.udp_wmem_min = 131072
net.ipv4.conf.all.arp_accept = 1
net.ipv4.conf.default.arp_accept = 1
net.ipv4.conf.all.arp_ignore = 1
net.ipv4.conf.default.arp_ignore = 1
vm.max_map_count = 262144
vm.swappiness = 0
vm.overcommit_memory = 0
fs.inotify.max_user_instances = 524288
fs.inotify.max_user_watches = 524288
fs.pipe-max-size = 4194304
fs.aio-max-nr = 262144
kernel.pid_max = 65535
kernel.watchdog_thresh = 5
kernel.hung_task_timeout_secs = 5
net.ipv6.conf.all.disable_ipv6 = 0
net.ipv6.conf.default.disable_ipv6 = 0
net.ipv6.conf.lo.disable_ipv6 = 0
net.ipv6.conf.all.forwarding = 1
02:29:15 MSK success: [master]
02:29:15 MSK [ConfigureOSModule] configure the ntp server for each node
02:29:15 MSK skipped: [master]
02:29:15 MSK [KubernetesStatusModule] Get kubernetes cluster status
02:29:15 MSK success: [master]
02:29:15 MSK [FATA] Unsupported container runtime: cri-o

Additional information

and dont forget about this #2221

@Nello-Angelo Nello-Angelo added the bug Something isn't working label Dec 2, 2024
@pixiake
Copy link
Collaborator

pixiake commented Dec 3, 2024

kubekey can be used to install the cluster if cri-o is already installed on the node.
And you should set the containerManager to crio.

  kubernetes:
    ...
    containerManager: crio

@Nello-Angelo
Copy link
Author

Nello-Angelo commented Dec 3, 2024

update docs

#Container Runtime, support: containerd, cri-o <-------- here, isula. [Default: docker]
containerManager: docker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants