4 ms·

Seems like only a year ago Docker changed how it used Virtualbox to boot VMs using machine (and caused me endless amounts of suffering trying to figure out how

Seems like only a year ago Docker changed how it used Virtualbox to boot VMs using machine (and caused me endless amounts of suffering trying to figure out how to fix it). Now it would seem they are getting rid of Virtualbox entirely with their own VM...which needs contributions.

avita1 10y ago
My understanding is not great, but it looks like they're bypassing a host VM entirely and using a shim (HyperKit) to talk to whatever virtualization the underlying OS supplies.
danieldk 10y ago
getting rid of Virtualbox entirely with their own VM... Not really. This builds heavily upon Hypervisor.framework, which is included in new OS X versions. Hypervisor.framework is pretty cool, because it allows for building VM applications that are sandboxed and don't require kernel modules. As a result, Hypervisor.framework applications can even be distributed via the App Store (see e.g. Veertu).
- lobster_johnson 10y ago
  I wonder if Vagrant intends to provide a Hypervisor.framework-based Linux backend. That would be cool. Edit: Experimental plugin: https://github.com/oldpatricka/vagrant-xhyve https://github.com/oldpatricka/vagrant-xhyve.
- fpoling 10y ago
  The drawback is that now VM manager is at mercy of what Hypervisor.framework provides. For example, Veertu does not support redirection of USB devices into VM because the framework does not support it. That makes it rather useless for my usage and I stick with VirtualBox for now. Of cause, this is not an issue for Docker as the framework covers all its needs.
rhinoceraptor 10y ago
I'm running the new beta native Docker for Mac, it is really nice. You install from the DMG, enter your password, and you're done. No more running 'eval $(docker-machine env dev)', no more having to delete the VM and rebuild it, etc.
- knz 10y ago
  Have your encountered any major bugs with Docker for OSX? I've been running docker-machine without any major issues for months but have noticed in the last few weeks that I need to reboot the VM lately due to weird caching issues.
  - toomuchtodo 10y ago
    I have constant connection problems between the Docker CLI and the Docker VM running Docker for OSX :/
    - knz 10y ago
      Thanks for the feedback.
    - justincormack 10y ago
      In recent updates? We have changed how this works in the last few releases, we hope it will be more stable.
      - zwischenzug 10y ago
        I had this also; will re-try a more recent version.
        avsm 10y ago
        Please do let us know if it persists, to beta-feedback@docker.com or on the forums.
  - rhinoceraptor 10y ago
amackera 10y ago
Docker is still pretty bleeding edge, and was never designed to work with Mac OS X or Windows from the get-go. The fact that the proposed experience for OS X and Windows is so good is a testament to how hard the community and the Docker team have been working! It's natural that there would be some growing pains.
- jcoffland 10y ago
  So you're saying it's really bad and that's why it's so good.

avita1 10y ago

My understanding is not great, but it looks like they're bypassing a host VM entirely and using a shim (HyperKit) to talk to whatever virtualization the underlying OS supplies.

danieldk 10y ago

getting rid of Virtualbox entirely with their own VM... Not really. This builds heavily upon Hypervisor.framework, which is included in new OS X versions. Hypervisor.framework is pretty cool, because it allows for building VM applications that are sandboxed and don't require kernel modules. As a result, Hypervisor.framework applications can even be distributed via the App Store (see e.g. Veertu).

lobster_johnson 10y ago
I wonder if Vagrant intends to provide a Hypervisor.framework-based Linux backend. That would be cool. Edit: Experimental plugin: https://github.com/oldpatricka/vagrant-xhyve https://github.com/oldpatricka/vagrant-xhyve.
fpoling 10y ago
The drawback is that now VM manager is at mercy of what Hypervisor.framework provides. For example, Veertu does not support redirection of USB devices into VM because the framework does not support it. That makes it rather useless for my usage and I stick with VirtualBox for now. Of cause, this is not an issue for Docker as the framework covers all its needs.

rhinoceraptor 10y ago

I'm running the new beta native Docker for Mac, it is really nice. You install from the DMG, enter your password, and you're done. No more running 'eval $(docker-machine env dev)', no more having to delete the VM and rebuild it, etc.

knz 10y ago
Have your encountered any major bugs with Docker for OSX? I've been running docker-machine without any major issues for months but have noticed in the last few weeks that I need to reboot the VM lately due to weird caching issues.
- toomuchtodo 10y ago
  I have constant connection problems between the Docker CLI and the Docker VM running Docker for OSX :/
  - knz 10y ago
    Thanks for the feedback.
  - justincormack 10y ago
    In recent updates? We have changed how this works in the last few releases, we hope it will be more stable.
    - zwischenzug 10y ago
      I had this also; will re-try a more recent version.
      - avsm 10y ago
        Please do let us know if it persists, to beta-feedback@docker.com or on the forums.
- rhinoceraptor 10y ago

amackera 10y ago

Docker is still pretty bleeding edge, and was never designed to work with Mac OS X or Windows from the get-go. The fact that the proposed experience for OS X and Windows is so good is a testament to how hard the community and the Docker team have been working! It's natural that there would be some growing pains.

jcoffland 10y ago
So you're saying it's really bad and that's why it's so good.