It's here: Docker 1.0
blog.docker.com
blog.docker.com
I've wanted to try it ever since pyTennessee, but it looked like it didn't make sense for spinning up a one-off hobby project. Without using it to grapple with the problems it is supposed to solve, I feel like I'd just be running through a tutorial which I could do just as easily when I actually need Docker.
One of the greatest things about Docker is it lets you consolidate your setup environments. You can great a handful of 2k scripts, store them in Dropbox, and then if you current development machine bites it, a simple "docker add <script>" gets you up and running exactly as before.
Docker lets you stop treating your personal machine as a server. And that's a beautiful thing.
Its basically a build script that is less than 100 lines, generally, so it is really easy to use.
Just add "FROM deis/python-runtime" to the top of your project and declare a CMD or an ENTRYPOINT in your Dockerfile and suddenly you have a python project installed and ready to go.
It doesn't mean modifying the Dockerfile.
It looks like a solution for https://github.com/dotcloud/docker/issues/1228 didn't make it into 1.0 after all.