Move host customizations to privileged containers

[shykes]

I would like to remove pipework and other host customizations from the core boot2docker before it's too late, and move to containers as a standard means of expressing and loading customizations into boot2docker.

Once people start relying on various out-of-band tools being present on the host, you just lost the real potential of boot2docker which is to expose 100% of a machine's functionality via a standard docker endpoint. Once you start walking down that slippery slope, suddenly you have 100 new pull requests like #91 and all of sudden you're just another bloated distro.

[tianon]

+1

[shykes]

This is especially important since we're considering b2d as a standard component of our Mac installer. If b2d becomes of a docker release we need to support it - and I don't want to support random hacks which rely on private docker APIs.

[moul]

👍

[bruienne]

Understood, and excellent point. I had the same feeling as I was going down what felt an awful lot like a slippery slope, trying to satisfy the pipework requirements.

[yosifkit]

Closing as this seems to be resolved. If you feel this issue was closed prematurely, please comment and let us know.