4 ms·

The promise of "Speed of containers and security of VMs" is enticing, but is there a simple 101/quickstart for somebody that just wants to run one container in

The promise of "Speed of containers and security of VMs" is enticing, but is there a simple 101/quickstart for somebody that just wants to run one container in this way? as in no Kubernetes, OpenStack, Multi-tenancy, nothing..... Just one bare-metal server, configured as KVM host, and how can I [run/start/stop] one Kata container? I feel like everyone just assumes you're a Kubernetes Pro and runs infrastructure at the scale of Google/FB/Amazon these days... :-(

kevinsimper 8y ago
That is where serverless is really awesome as it give you scale and flexibility, and the providers behind are using containers
pliu 8y ago
The documentation for kata seems fairly straightforward for a single host install. Install the kata packages, modify docker daemon to change the run time, then use Docker the usual way. https://github.com/kata-containers/documentation/blob/master/install/docker/ubuntu-docker-install.md https://github.com/kata-containers/documentation/blob/master...
swozey 8y ago
k8s is really just the scheduler and gives you a uniform way to deploy the "vm" containers in the usual scenario. With k8s you can have workloads run on different runtimes like trusted=runc, untrusted=kata, etc and this is even easier now with RuntimeClass which you can write right inside of a regular k8s deployment yaml. Kata is actually just several binaries that talk via grpc (kata-agent, shim, proxy, runtime) and interface with QEMU/NEMU. For instance kata-proxy proxies commands over virtios serial interface that's exposed via QEMU. You could install the binaries and qemu-lite and have a similar system but I'm not really sure how you'd benefit as it's the management through k8s that really won me over. I think in your scenario you'd just be making very complicated QEMU vms. I've linked this to the contribs, maybe they have some thoughts.

kevinsimper 8y ago

That is where serverless is really awesome as it give you scale and flexibility, and the providers behind are using containers

pliu 8y ago

The documentation for kata seems fairly straightforward for a single host install. Install the kata packages, modify docker daemon to change the run time, then use Docker the usual way. https://github.com/kata-containers/documentation/blob/master/install/docker/ubuntu-docker-install.md https://github.com/kata-containers/documentation/blob/master...

swozey 8y ago

k8s is really just the scheduler and gives you a uniform way to deploy the "vm" containers in the usual scenario. With k8s you can have workloads run on different runtimes like trusted=runc, untrusted=kata, etc and this is even easier now with RuntimeClass which you can write right inside of a regular k8s deployment yaml. Kata is actually just several binaries that talk via grpc (kata-agent, shim, proxy, runtime) and interface with QEMU/NEMU. For instance kata-proxy proxies commands over virtios serial interface that's exposed via QEMU. You could install the binaries and qemu-lite and have a similar system but I'm not really sure how you'd benefit as it's the management through k8s that really won me over. I think in your scenario you'd just be making very complicated QEMU vms. I've linked this to the contribs, maybe they have some thoughts.