I&#x27;m keen on unikernels too. At work I&#x27;ve argued that we should build a Xen backend for Garden so that Cloud Foundry can drive unikernel apps on equal footing with buildpack staged containers, docker containers and .NET apps. Mind you, I argue for a lot of things at work, very few of which are ever picked up; probably for the best.<p>But for all the virtues of unikernels, an awful lot of software assumes a linuxy userland. Outside of consciously isolated universes like Java and .NET, it might be tricky to get traction.<p>As for devops, the missing bit isn&#x27;t the sexy stuff -- the parts that locate and monitor processes running in containerised environments. Kubernetes, Mesos, Diego and the dozens of others popping up every week are busy solving that.<p>What seems to be forgotten is that, as this article mentions, you still need a sane build-and-verify pipeline. Tools like Puppet, Chef and the like can be seen as image-building toolkits. Buildpacks already know how to take various stacks and turn them into runnable images (on Heroku or Cloud Foundry). Docker is a step backwards, in some respects.<p>Disclaimer: I work for Pivotal, the company which donates the majority of engineering effort to Cloud Foundry.