Only one part has you run scripts against your actual system. The http://get.docker.io/ script handles a lot of the variables and performs some basic checks. You can always read it before running it, and you can always install those packages by hand. Every thing else runs inside a separate container that is isolated from the main system; the launcher script is simply copying the configuration file into environment variables and instructing docker to pull the correct images.
I’ve had problems with this too… but I always thought it was something I was doing wrong. In fact, I just fired up a plain ubuntu vm and the key still did not copy correctly. I’ve got a vm packaged with the issue if needed.
I took some time and thought about this. It looks like it works if you bootstrap while fully logged in as root; and not if you escalate via sudo. If you go the sudo route, it tries to create a key for the non-root user but never copies it over.
What does not work exactly? Commands are being run against the docker container and not your actual system, so it does not require real or sudo root access. What step does it seem to hang on?