We do "just run containers" for our entire CI pipeline. It's all lxc/lxd and just a bunch of shell scripts to start/stop them. Works surprisingly well. So if yo

We do "just run containers" for our entire CI pipeline. It's all lxc/lxd and just a bunch of shell scripts to start/stop them. Works surprisingly well. So if you are just using containers as a sandboxed work runner then you don't need anything fancy. The issue is that I think people would like to pretend that containers are just like VMs and this is where things start to break down. They're not VMs in the sense that none of the tried and true methods for orchestrating VMs is available. You need new solutions for networking, new solutions for storage, new failover patterns, new tools for clustering and organizing them, new application patterns, etc. Basically all the stuff that would have been handled by the hypervisor and the software defined networking layer is now all of a sudden in your face and you need some way to deal with it.