| kata-irc-bot | <fidencio> What does MVM mean, Hengql? Also, which comments / commits are you referring to? Mind to share? | 12:50 |
|---|---|---|
| kata-irc-bot | <fidencio> Also, how are you using Kata Containers? With Kubernetes? | 12:51 |
| kata-irc-bot | <fidencio> Cool, that's from me. | 14:19 |
| kata-irc-bot | <chenhengqi> We are not using Kata Containers with Kubernetes. | 14:20 |
| kata-irc-bot | <fidencio> Kata Containers is only support with the latest version of Docker, or with Kubernetes. May I ask how are you using it so far? | 14:21 |
| kata-irc-bot | <chenhengqi> We plan to impl some orchestration system on top of Kata Containers. | 14:23 |
| kata-irc-bot | <chenhengqi> ```$ ctr run --cni --runtime io.containerd.run.kata.ch -t --rm docker.io/library/ubuntu:latest network-test /bin/bash``` I run this command, and notice that the bridge device and veth device are created. But there is no tap device created for the VM. | 14:25 |
| kata-irc-bot | <chenhengqi> • By default, the Internetworking model is set to `tcfilter`, but I don't see any TC filter enabled | 14:26 |
| kata-irc-bot | <chenhengqi> Quoted from the doc | 14:30 |
| kata-irc-bot | <chenhengqi> > This is a very namespace-centric approach as many hypervisors or VM Managers (VMMs) such as `virt-manager` cannot handle `veth` interfaces. Typically, `TAP` interfaces are created for VM connectivity. > To overcome incompatibility between typical container engines expectations and virtual machines, Kata Containers networking transparently connects `veth` interfaces with `TAP` ones using Traffic Control: | 14:30 |
| kata-irc-bot | <fidencio> That's something known to nor work, AFAIR. | 14:30 |
| kata-irc-bot | <fidencio> Could you give it a try with nerdctl instead? | 14:30 |
| kata-irc-bot | <chenhengqi> OK, will try. | 14:34 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!