-
Notifications
You must be signed in to change notification settings - Fork 2k
Update VMware Fusion and vSphere driver to run boot2docker 1.6.0 #1034
Conversation
- Update custom ISO to docker 1.6.0. - Shared folder support for VMware Fusion. - Updated bats test for Fusion. Signed-off-by: Fabio Rapposelli <[email protected]>
Boom!! Thanks @frapposelli |
Thanks! |
Awesome! Thank you @frapposelli |
@frapposelli Thanks! Just curious is it faster than NFS? |
@Maxim-Filimonov not always faster than NFS, @mitchellh has done an interesting analysis of the various sync options with local hypervisors here http://mitchellh.com/comparing-filesystem-performance-in-virtual-machines |
LGTM 👍 |
Update VMware Fusion and vSphere driver to run boot2docker 1.6.0
Thanks - this is rad! The performance of VMware Fusion shared volumes is great, even with fairly sizable projects. I've ditched my Vagrant boot2docker/NFS setup in my dev environment for the time being, and I'm also able to use docker-machine's interface to a larger extent. After creating my VM with docker-machine, I went into Fusion's GUI and tweaked a few more things. For example, the processor was set to 4 cores - I'm on a 2 core machine (Fusion displayed a performance warning in that section). I also went to the Hard Disk section and pre-allocated the disk. |
@philm thanks for the feedback! @frapposelli i believe the default number of CPUs should default to the host system correct? |
In docker#615, the helper function `machine()` was created and used within the vmwarefusion test suite (amongst others) to wrap a platform-specfic binary during the test suite. In docker#1034, it appears that this name was changed to the normal docker-machine binary, which can incoke the system-installed one, not the recently compiled one, potentially testing the incorrect binary. See: - docker#615 (comment) - https://github.com/docker/machine/pull/1034/files#diff-62c88a2fede921556dbdeead731596b2R14
In docker#615, the helper function `machine()` was created and used within the vmwarefusion test suite (amongst others) to wrap a platform-specfic binary during the test suite. In docker#1034, it appears that this name was changed to the normal docker-machine binary, which can incoke the system-installed one, not the recently compiled one, potentially testing the incorrect binary. See: - docker#615 (comment) - https://github.com/docker/machine/pull/1034/files#diff-62c88a2fede921556dbdeead731596b2R14 Signed-off-by: Mike Fiedler <[email protected]>
use new 'daemon' command
Fixes #1021 #1020 #641 #532 #430