I'm always afraid of 1.0 release stuff for actual production environments, despite who releases it
1) Works for my application.
2) Won't get my head chopped off.
The second is what most developers working inside a hierarchy really want. I am always torn in trying to keep up with new things, because reliability is generally not the focus of new products.
You can use OpenVZ right now for similar things, but it isn't as easy to create small single-use containers.
The nice thing OpenVZ has that docker doesn't currently support is mounting a Host directory (read-only or read-write) into the OpenVZ container so you can easily share lots of data to many containers with one copy. Right now, docker supports sharing volumes between containers, but not with the Host system.
For example, you can make very small OpenVZ containers by using common /usr, /lib, /lib64 directories and mounting them read-only in all of your containers. It's easy to bring up OpenVZ on a Centos6 machine and you can run Ubuntu containers in it if you like.
I have nothing against Docker and hope they keep adding features, but my current experience is with OpenVZ.
https://github.com/dotcloud/docker/pull/602
Dockerlite doesn't have those features, though (keep in mind that dockerlite is just a playground for funky features, nothing else!)
It's a killer feature and extremely useful.