4 ms·

They don't seem to have written any code yet. [1] So what we have at this point is a marketing website about their ambition and goals? [1]https://github.com/ka

They don't seem to have written any code yet. [1] So what we have at this point is a marketing website about their ambition and goals? [1]https://github.com/kata-containers/runtimes https://github.com/kata-containers/runtimes

paulfurtado 9y ago
The code comes from Intel's Clear Containers and hyper. The interesting bit is that the tech is now part of the openstack foundation, under the name Kata Containers. At Kubecon yesterday, they did a demo, showing a fork bomb taking out a container, but not the host. It actually seems nearly ready to use.
- redtuesday 9y ago
  Can't you just combat fork bombs with e.g docker run --pids-limit=64
  - paulfurtado 9y ago
    Yes, there are several ways to combat fork bombs (ulimits or pid namespaces). This was purely for the sake of the live demo that required a kernel crash example, there are certainly other ways to combat it.
tecleandor 9y ago
It is comprised by many parts that, already, have seen development as: Kata Agent: https://github.com/kata-containers/agent https://github.com/kata-containers/agent Kata Shim: https://github.com/kata-containers/shim https://github.com/kata-containers/shim Kata Proxy: https://github.com/kata-containers/proxy https://github.com/kata-containers/proxy KSM Throttler: https://github.com/kata-containers/ksm-throttler https://github.com/kata-containers/ksm-throttler And some forks to provide for their necessities, I suppose, as: Linux Kernel: https://github.com/kata-containers/linux https://github.com/kata-containers/linux QEMU: https://github.com/kata-containers/qemu https://github.com/kata-containers/qemu
mugsie 9y ago
There does seem to be a fair bit left to write (or clean up and open source from Hyper.sh and Intel) e.g. the entire testing repo is empty I would suggest we are looking at a conference driven development release
- aleeland 9y ago
  I am a product manager for Intel's Clear Containers and am also working in this community with Kata. We are still under development and merging Intel Clear Containers (CC) and Hyper.sh runV. Our 1.0 release is scheduled for March timeframe, at which point we plan to have a migration path for customers using runv or CC. We launched this week so that we can build our community and continue to merge the code in the open!

paulfurtado 9y ago

The code comes from Intel's Clear Containers and hyper. The interesting bit is that the tech is now part of the openstack foundation, under the name Kata Containers. At Kubecon yesterday, they did a demo, showing a fork bomb taking out a container, but not the host. It actually seems nearly ready to use.

redtuesday 9y ago
Can't you just combat fork bombs with e.g docker run --pids-limit=64
- paulfurtado 9y ago
  Yes, there are several ways to combat fork bombs (ulimits or pid namespaces). This was purely for the sake of the live demo that required a kernel crash example, there are certainly other ways to combat it.

tecleandor 9y ago

It is comprised by many parts that, already, have seen development as: Kata Agent: https://github.com/kata-containers/agent https://github.com/kata-containers/agent Kata Shim: https://github.com/kata-containers/shim https://github.com/kata-containers/shim Kata Proxy: https://github.com/kata-containers/proxy https://github.com/kata-containers/proxy KSM Throttler: https://github.com/kata-containers/ksm-throttler https://github.com/kata-containers/ksm-throttler And some forks to provide for their necessities, I suppose, as: Linux Kernel: https://github.com/kata-containers/linux https://github.com/kata-containers/linux QEMU: https://github.com/kata-containers/qemu https://github.com/kata-containers/qemu

mugsie 9y ago

There does seem to be a fair bit left to write (or clean up and open source from Hyper.sh and Intel) e.g. the entire testing repo is empty I would suggest we are looking at a conference driven development release

aleeland 9y ago
I am a product manager for Intel's Clear Containers and am also working in this community with Kata. We are still under development and merging Intel Clear Containers (CC) and Hyper.sh runV. Our 1.0 release is scheduled for March timeframe, at which point we plan to have a migration path for customers using runv or CC. We launched this week so that we can build our community and continue to merge the code in the open!