Can you run Dind as a service on Tutum so that Drone can use it?
It turns out you can and it all seems to work just fine :)
I have my "node" in tutum speak, which has docker running on it, but it's tutum's docker that you can interact with to some extent using their api.
Inside that I have an off the shelf dind container (docker in docker) running as a daemon with its listening port specified in the PORT environment variable (which wrapdocker picks up). That port is exposed (not publicly) using tutum's interface.
Drone is configured from another off the shelf container (for github etc) and it's linked to the dind service so that drone's DOCKER_HOST environment variable can be set to: {linked dind alias}:{port number}
...and it works :)
I feel like this should have been clear from the start but I just don't think that I believed it!