Checking Kata compatibility
time="2020-07-02T02:16:45Z" level=warning msg="modprobe insert module failed: modprobe: ERROR: could not insert 'vhost': Operation not permitted\n" arch=amd64 error="exit status 1" module=vhost name=kata-runtime pid=25049 source=runtime time="2020-07-02T02:16:45Z" level=error msg="kernel property not found" arch=amd64 description="Host kernel accelerator for virtio" name=vhost pid=25049 source=runtime type=module time="2020-07-02T02:16:45Z" level=warning msg="modprobe insert module failed: modprobe: ERROR: could not insert 'vhost_net': Operation not permitted\n" arch=amd64 error="exit status 1" module=vhost_net name=kata-runtime pid=25049 source=runtime time="2020-07-02T02:16:45Z" level=error msg="kernel property not found" arch=amd64 description="Host kernel accelerator for virtio network" name=vhost_net pid=25049 source=runtime type=module time="2020-07-02T02:16:45Z" level=warning msg="modprobe insert module failed: modprobe: ERROR: could not insert 'vhost_vsock': Operation not permitted\n" arch=amd64 error="exit status 1" module=vhost_vsock name=kata-runtime pid=25049 source=runtime time="2020-07-02T02:16:45Z" level=error msg="kernel property not found" arch=amd64 description="Host Support for Linux VM Sockets" name=vhost_vsock pid=25049 source=runtime type=module time="2020-07-02T02:16:45Z" level=error msg="ERROR: System is not capable of running Kata Containers" arch=amd64 name=kata-runtime pid=25049 source=runtime ERROR: System is not capable of running Kata Containers
Aborted. Current system does not support Kata Containers.
Kata Setup done.
so what is the basic requirement to make it work, it seems something missing in the prerequisite..
What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
Arktos version (use kubectl version):
Cloud provider or hardware configuration:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Network plugin and version (if this is a network-related bug):
so what is the basic requirement to make it work, it seems something missing in the prerequisite..
What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
):cat /etc/os-release
):uname -a
):