Ammar Bandukwala

It's probably hanging on a git prompt. Try `pstree $(pidof sail)`

The title of this issue doesn't make sense with the message

Made a more specific issue #172

because of the pitfalls outlined here https://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/ we'll just mount in the docker socket and provide an `OUTER_ROOT` env with the path to chroot from the host's perspective.

discussed in person that we can always provide the OUTER_ROOT env and leave it to the user to bind mount the socket in with a `share` directive. Should definitely provide...

I don't see that in that doc?

Proper dind is supposedly unreliable according to that blog post... Going to close this for now.

> Docker-in-Docker: the bad However, contrary to popular belief, Docker-in-Docker is not 100% made of sparkles, ponies, and unicorns. What I mean here is that there are a few issues...

The only other issue I see is the build cache... We're trying to promote short-lived environments so Docker in the container may be slow.

Wouldn't we want to enable dind in our ubuntu-dev base image, forcing every container to be privileged?