Completely agree. You can do something like this: 1. Statically compile your application so that it can run standalone. For ruby, python or java that means inc

Completely agree. You can do something like this: 1. Statically compile your application so that it can run standalone. For ruby, python or java that means including the interpreter and any dynamic libraries. Hard at first, but once you have a build setup it's pretty straightforward 2. Bundle your application with its assets in a zip file or tarball 3. Make it so that your application has a well defined set of resources it uses that are isolated from other applications. For example with a database you might have a `your-app\data` folder where it stores the actual database. Also make sure you are careful with ports 4. Pass around configuration via environment variables that you hand to your application (ie: DATABASE_HOST=127.0.0.1) With a setup like that you can build a sensible stack that runs anywhere. You don't need containers: 1. You don't need the protection: just don't write processes which clobber other processes. It's not that hard. 2. The reuse mechanism seems cool, but it comes with baggage. Which version of ubuntu are you starting with? Does it include the latest updates to shared libraries? If it does how do you know that your application will still run down the road? And if it doesn't, how are you keeping on top of security updates? 3. Containers, as envisioned by docker, are way overkill. Why do you need an entire ubuntu to run a simple web app?