You can’t run Docker within containers that run within the user space. These are called light-weight containers and one of those are OpenVZ and LXC. On the other hand, KVM, Xen, VMWare and other “hardware virtualization” technologies that load a custom kernel and separate hardware components into the logical abstractions can easily run Docker within the VM itself because the VM is not aware that it is being virtualized.
We have a couple of clients running Docker and our documentation on installing CrossBox inside of a Docker container can give you a general idea on how to get some software working within Docker. It is relatively easy and usually, the most difficult part is port mapping (passing the traffic from the host node to the Docker container). You install everything else as usual after you enter the container’s bash.
Personally, Docker is really good and one of the few things that I hate doing is entering a Docker container:
docker exec -it 88982f9169b45259d04eb5df211fff4c3dd57c8a1ea6b60d9020bf7b3bdab105 bash
and that huge hash is a container’s ID which you get with: