Packer only build process

[dduportal]

Hi !

This PR introduce a new build process based only on packer (the goal was to not download a big vagrant box nor a big Docker image).

First, it contains these PRs :

• SSL docker port support : Adding docker SSL tcp port #71
• Packer 0.7.x compatibility(Parallels provider) : Packer 7 compatibility #70
• Enabling default vagrant vboxsf share with docker 1.3.x : Enabling the default vagrant share while boot2docker 1.3.0 embed vboxsf #69

Secondly, it add these changes :

• Correcting the 42 layers AUFS bug, we can now use 127 layers in docker (See : boot2docker 1.2 cannot run or build image over 42 layers on ext4 with aufs boot2docker/boot2docker#531 (comment) - in brief we create a partition and format it isntead of formatting the whole sda device)
• Moving to boot2docker 1.3.1 (instead of 1.3.0)
• Packer now use a shell script instead of inline script

It will use the original boot2docker iso file, and tune it using a provision script + boot2docker perisstence options added recently.
The boot2docker documentation says that if you have a userdata.tar in //var/lib/boot2docker, then it will be unarchived in /home/docker/ at the end of the boot : it's seems to be a good idea to push the vagrant ssh keys here no ?
See https://github.com/boot2docker/boot2docker#upgrade-the-boot2docker-vm-image

[legal90]

@dduportal About enabling SSL: How does machine certificates will be verified on the host side? I have not found any manipulations with DOCKER_CERT_PATH
For example, docker-machine utility copies CA from each guest VM to the host. But I don't see something similar here. How does it works for you?