3 ms·
An interesting fact I think is worth mentioning is that Docker for Mac uses a forked and currently closed version of xhyve, and not the same xhyve that we can f
by Scorpiion 10y ago
An interesting fact I think is worth mentioning is that Docker for Mac uses a forked and currently closed version of xhyve, and not the same xhyve that we can find on Github. The last commit to open source xhyve was May 27.
With that said Docker has plans to open source it, I wonder if that will happen soon as they declare Docker for Mac ready for production. That would imply that the xhyve port also should be ready be contributed back or spin out into a new project (the quote below said they were not sure if they wanted to contribute back or make a new project).
Personally I think the "right thing to do" would be to contribute back to xhyve, at the same time I have a feeling it's more valuable for Docker Inc to "own" and control their own fork/project so I would guess they will go down that path instead (it would still be open source, just under a different project name).
Source: https://news.ycombinator.com/item?id=11356293 https://news.ycombinator.com/item?id=11356293
EDIT: I stand corrected, see talex5 comment below, I had missed the hyperkit announcement.
- talex5 10y agoI think this is what you're looking for: https://github.com/docker/hyperkit https://github.com/docker/hyperkit Source: https://blog.docker.com/2016/05/docker-unikernels-open-source/ https://blog.docker.com/2016/05/docker-unikernels-open-sourc...
- Scorpiion 10y agoOh, my bad, thanks for the correction! :)