| *** stackedsax has joined #kata-general | 05:00 | |
| *** lpetrut has joined #kata-general | 08:03 | |
| *** gwhaley has joined #kata-general | 09:04 | |
| *** lpetrut has quit IRC | 09:32 | |
| *** gwhaley has quit IRC | 11:52 | |
| *** gwhaley has joined #kata-general | 12:58 | |
| *** Bhujay has joined #kata-general | 15:15 | |
| *** Bhujay has quit IRC | 15:16 | |
| kata-irc-bot | <cody> newbie question here.. do Kata containers continue to use CRI-O or other linux container runtime inside of the light weight VMs to manage the namespace and cgroups for the process. Thinking about K8s pods with multiple containers… I assume they behave like standard containers inside the VMs? | 17:55 |
|---|---|---|
| *** gwhaley has quit IRC | 18:04 | |
| kata-irc-bot | <raravena80> @cody yes, it behaves pretty much like containers in a VM. In the case of k8s Kata uses a VM per pod and you can have many containers in a pod. You can use either containerd or CRIO as interface to kata (or any other runtime for that matter) | 18:09 |
| kata-irc-bot | <eric.ernst> We utilize libcontainer pkg inside the VM. This is the basis of runc | 18:12 |
| kata-irc-bot | <cody> @raravena80 Thanks! That was exactly what I was looking to find out. | 19:42 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!