# Native Docker for macOS?

**URL:** <https://community.localwp.com/t/native-docker-for-macos/99>\
**Category:** Feature requests\
**Created:** [December 2, 2016, 12:56pm UTC](https://community.localwp.com/t/native-docker-for-macos/99 "2016-12-02T12:56:38Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![soderlind](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/soderlind/32/24675_2.png) [@soderlind](https://community.localwp.com/u/soderlind)\
**Post date:** [December 2, 2016, 12:56pm UTC](https://community.localwp.com/t/native-docker-for-macos/99/1 "2016-12-02T12:56:39Z")

</div>

Any reason why you are using boot2docker and virtualbox and not the native Docker for macOS ?

---

<div class="post-metadata">

**Author:** ![clay](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/clay/32/8248_2.png) [@clay](https://community.localwp.com/u/clay)\
**Post date:** [December 2, 2016, 3:14pm UTC](https://community.localwp.com/t/native-docker-for-macos/99/2 "2016-12-02T15:14:32Z")

</div>

Right now Docker for Mac is still pretty new as is xhyve (what it uses instead of VirtualBox).

I know VirtualBox isn’t everyone’s favorite software, but it is very mature, very stable, and fast. I’ve looked at benchmarks of VirtualBox vs. xhyve and CPU performance is 2x better in VBox than it is in xhyve.

With that said, we’re totally open to xhyve but we want to wait for it to mature first.

---

<div class="post-metadata">

**Author:** ![soderlind](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/soderlind/32/24675_2.png) [@soderlind](https://community.localwp.com/u/soderlind)\
**Post date:** [December 2, 2016, 7:40pm UTC](https://community.localwp.com/t/native-docker-for-macos/99/3 "2016-12-02T19:40:25Z")

</div>

ok … thanks for the quick answer. Local works like a charm, just moved from VVV.

---

<div class="post-metadata">

**Author:** ![rmpel](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/rmpel/32/4529_2.png) [@rmpel](https://community.localwp.com/u/rmpel)\
**Post date:** [December 21, 2016, 7:01pm UTC](https://community.localwp.com/t/native-docker-for-macos/99/4 "2016-12-21T19:01:52Z")

</div>

I thought it might have to do with the planned windows version. Using virtualbox instead of native docker provides a uniform and cross platform solition with virtualbox as only os specific piece if software (apart from local)

I may be wrong, but at least it makes sense 😛

---

<div class="post-metadata">

**Author:** ![philby](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/philby/32/4565_2.png) [@philby](https://community.localwp.com/u/philby)\
**Post date:** [March 1, 2017, 10:25am UTC](https://community.localwp.com/t/native-docker-for-macos/99/5 "2017-03-01T10:25:51Z")

</div>

The benchmarks I found seem to show CPU speed to be about the same, but significantly slower disk access.

One advantage of not using VirtualBox would probably be RAM usage. I’d really love local to be as frugal (and fast) as, say, Laravel Valet –– while still remaining the far more professional solution, of course 🙂

---

<div class="post-metadata">

**Author:** ![diddledan](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/diddledan/32/4914_2.png) [@diddledan](https://community.localwp.com/u/diddledan)\
**Post date:** [July 22, 2017, 2:37pm UTC](https://community.localwp.com/t/native-docker-for-macos/99/6 "2017-07-22T14:37:35Z")

</div>

why do you care what hypervisor the docker system uses? just be a consumer! you shouldn’t be trying to ship your own implementation of docker, but should just use whatever is provided by the user/system. on linux, use docker. on mac, use docker. on windows, use docker. this is the promise of docker, yet you are breaking the guaranteed compatibility by trying to ship your own runtime!

---

<div class="post-metadata">

**Author:** ![philby](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/philby/32/4565_2.png) [@philby](https://community.localwp.com/u/philby)\
**Post date:** [September 26, 2017, 6:38am UTC](https://community.localwp.com/t/native-docker-for-macos/99/7 "2017-09-26T06:38:27Z")

</div>

Looks like Docker for Mac at least is slowly getting there: [https://stories.amazee.io/docker-on-mac-performance-docker-machine-vs-docker-for-mac-4c64c0afdf99](https://stories.amazee.io/docker-on-mac-performance-docker-machine-vs-docker-for-mac-4c64c0afdf99)

---

<div class="post-metadata">

**Author:** ![philby](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/philby/32/4565_2.png) [@philby](https://community.localwp.com/u/philby)\
**Post date:** [October 3, 2017, 7:58am UTC](https://community.localwp.com/t/native-docker-for-macos/99/8 "2017-10-03T07:58:08Z")

</div>

One advantage native Docker might possibly have: longer battery runtime.

The VBoxHeadless process is the one single process on my Mac that _always_ comes up as “using significant energy”, regardless of whether it is doing anything at all or just sitting there idly, with no site in Local running.

 ![58](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/2X/4/443e4d747f583c332f933ae8f517c4f1a5858850.png)
