Comment Re: No (Score 2) 252
That sounds very much along my thoughts. Some workloads are supremely better at being containerized (such as things you would otherwise consider using a chroot jail for), and some aren't. But Docker allows you to easily replicate the same kind of environment for local development as production, which avoids the common "it works on my machine" problems even Vagrant VMs can have.
And then there are CaaS offerings like Amazon's Lambda/API Gateway and CodeBuild services that use containers even though you're not managing the actual container spinup/tear down yourself. CodeBuild is a great example of containerization; it's much more efficient/cost-cutting at small and medium compilation workloads than paying to run one or more full time Jenkins servers. (If you're thrashing Jenkins with continuous builds, then it might be cheaper to use EC2. Same with API Gateway and ECS; there is a break even point to running your own Docker clusters or instances vs using the other services, though that also means more operational overhead to manage those systems.)
Is containerization always best? No, it's just another tool in the arsenal. Knowing when to use what tool is always important.