[kkwak]

containers are implemented via cgroups (and others) and share the kernel. I presume with a unikernel, you'll not be sharing the kernel, obviously.. So concept of a "container" is there and probably the orchestration via kubernetes is all still valid up the stack, so it makes sense to call that "containers" still.

[AzzieElbab]

Unikernel should run directly on hypervisor. Not sure this plays along with multiple levels of virtualization in today's clouds.

[eyberg]

It does to a degree but there is immense confusion on how it does. For example with OPS https://ops.city (I'm associated with the project) we deploy directly to AWS or GCloud as an ami or cloud image not orchestrating qemu on top of an existing linux image. A lot of people until they have actually tried booting one are thoroughly confused on this process.

You could play on top of google nested virt or ami's 'bare metal' but both of those would have performance taxes.

I think in the coming years we'll see the big public clouds refactor their environments to support these in a better fashion.