Hacker News Reader

Comment by kordless | Hacker News Reader

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.

View on HN

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).

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.

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.

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.

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.

I have constant connection problems between the Docker CLI and the Docker VM running Docker for OSX :/

In recent updates? We have changed how this works in the last few releases, we hope it will be more stable.

I had this also; will re-try a more recent version.

Please do let us know if it persists, to beta-feedback@docker.com or on the forums.

I had it crash a couple times when it printed lots of text from the container to the terminal. I haven't had that happen since the update from today, though.

Thanks for the feedback.

This: https://forums.docker.com/t/file-access-in-mounted-volumes-e...

Mounting sockets as volumes no longer works. This broke a few things I was doing with sibling builds (-v /var/run/docker.sock:/var/run/docker.sock)

Wow that sounds awesome! Are there any estimates of when this will be an open beta for everyone? Very excited to try it out!

Docker ID: shuber

I'm not sure, I was on the waiting list for a while, I've been in the beta for about two weeks now.

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.

So you're saying it's really bad and that's why it's so good.

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.

Reply on news.ycombinator.com