Really looking forward to Docker being 1.0. What you want to do is build a single package of everything your application needs (which includes the application

Really looking forward to Docker being 1.0. What you want to do is build a single package of everything your application needs (which includes the application code and all dependencies -- libc and up), then copy that package to the production servers. It shouldn't matter if your application server has Ruby 1.9.3 and you need 2.0. It shouldn't matter if the last deploy of your app needs Nokogiri compiled against libxml 2.8 and you now need 2.9. It shouldn't matter if you are running 5 different apps with 5 completely different set of dependencies on the same machine. It shouldn't matter if you need to use the asset pipeline. It shouldn't matter if github or rubygems drops out half-way through the deploy process. All the production server should get is a single package of all that your application needs, then a 'restart application' command. Docker should be able to handle all this simply.