> since Joyent has implemented their own docker client Not our own docker client, our own Docker engine, https://github.com/joyent/sdc-docker https://github.co

> since Joyent has implemented their own docker client Not our own docker client, our own Docker engine, https://github.com/joyent/sdc-docker https://github.com/joyent/sdc-docker , which was necessary for the whole DC to be the host. For a taste of the details see https://www.joyent.com/developers/videos/bryan-cantrill-virtualizing-the-docker-remote-api-with-triton https://www.joyent.com/developers/videos/bryan-cantrill-virt... . Your larger point is correct, we're still working hard every day to add increase the support particularly for the newer docker apis and extensions. Now, docker-compose 1.2 is working in the production datacenters with docker-compose 1.3 in the east-3b (beta) dc. https://www.joyent.com/developers/triton-faq https://www.joyent.com/developers/triton-faq https://github.com/joyent/sdc-docker/blob/master/docs/api/divergence.md https://github.com/joyent/sdc-docker/blob/master/docs/api/di...