| kata-irc-bot | <tommylikehu> hey team, I am trying to setup a kata environment on my baremetal server, and the kata-runtime check command failed as below: ERRO[0000] /etc/kata-containers/configuration.toml: host system doesn’t support vsock: stat /dev/vhost-vsock: no such file or directory arch=amd64 name=kata-runtime pid=4357 source=runtime does this mean I have unsatisfied hardware or I am missing dependencies or others | 01:19 |
|---|---|---|
| kata-irc-bot | <bergwolf> @tommylikehu your host kernel doesn't support vhost-vsock. you may need `modprove vhost-vsock` or you cannot use QEMU as your vmm. cloud-hypervisor and firecracker otoh do not need vhost-vsock to work. | 03:10 |
| kata-irc-bot | <yadzhang> Kata not support k8s memory-medium empty-dir which specify sizeLimit？I take the test and find the memory emptydir size in guest is always half to vm default memory size. | 05:27 |
| kata-irc-bot | <tommylikehu> @bergwolf thanks，my kernel is 4.4, looks like I need to upgrade host kernel? `Linux kernel: Upstream since Linux 4.8`: https://wiki.qemu.org/Features/VirtioVsock | 06:25 |
| kata-irc-bot | <tommylikehu> @bergwolf so finally I end up docker integration not supported since kata 2 https://github.com/kata-containers/runtime/issues/3038 :,( ? | 09:17 |
| kata-irc-bot | <liubin0329> I think the `size` option is not passed to Kata Containers. The empthDir is prepared by kubelet and at the host side(https://github.com/kubernetes/kubernetes/blob/4d78db54a58e250b049c4fe17ac484e5c3ec662d/pkg/volume/emptydir/empty_dir.go#L328-L333) and kubelet only passed the mounted path to lower runtime because the CRI has no mount options defined( | 10:46 |
| kata-irc-bot | https://github.com/kubernetes/cri-api/blob/d0b5e990533cc3d30a54803c19a218d5ed13fce1/pkg/apis/runtime/v1/api.proto#L194-L208 ) | 10:46 |
| kata-irc-bot | <liubin0329> ``` tmpfs has three mount options for sizing: size: The limit of allocated bytes for this tmpfs instance. The default is half of your physical RAM without swap. If you oversize your tmpfs instances the machine will deadlock since the OOM handler will not be able to free that memory.``` | 10:47 |
| kata-irc-bot | <bergwolf> yup, you can try `nerdctl` if you want something similar as docker | 11:54 |
| kata-irc-bot | <liubin0329> I crated an issue https://github.com/kata-containers/kata-containers/issues/2438 to track this | 13:39 |
| kata-irc-bot | <eli.rozen> Hi all! Does anyone understand the Kata shutdown sequence and can explain it? | 18:34 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!