Fig 1.0: Boot2docker compatibility and more

Re:Fig 1.0: Boot2docker compatibility and more by gdw2 on Friday October 17, 2014 @02:20PM (#8472504)

Similar ends, but different means. Vagrant would launch a full-blown VM (likely on the order of several minutes), whereas fig'ing will start a container (on the order of a few seconds).

[ Parent | on HN ]

Re:Fig 1.0: Boot2docker compatibility and more by nailer on Friday October 17, 2014 @04:10PM (#8473076)

Fig still requires boot2docker, which uses VirtualBox.

See linked page at https://docs.docker.com/installation/mac/

Note VirtualBox is one of the only modules blacklisted by the Linux kernel not for being proprietary (it's Open Source) but because it's terrible.

http://www.phoronix.com/scan.php?page=news_item&px=OTk5Mw

[ Parent | on HN ]

Re:Fig 1.0: Boot2docker compatibility and more by zenlikethat on Friday October 17, 2014 @05:12PM (#8473408)

Fig only requires boot2docker if you are not working directly on Linux, this is true for docker itself as well.

We agree that VBox is not ideal but it is free and we would like to have other options (Fusion, HyperV) available in the future as well.

[ Parent | on HN ]

Re:Fig 1.0: Boot2docker compatibility and more by cpuguy83 on Sunday October 19, 2014 @07:38AM (#8477972)

boot2docker is a tiny Linux distro and does not require any specific virtualization tool, or even virtualization at all.

For the sake of simplicity and distribution the OSX and Windows installers package boot2docker with Virtualbox.

[ Parent | on HN ]

Re:Fig 1.0: Boot2docker compatibility and more by samuel1604 on Friday October 17, 2014 @11:39PM (#8474534)

I use fig with volume from my mac under vmware without any problem

[ Parent | on HN ]