It could be that a permission popup shows while saving this file. So therefore this line exports the directory /System/Volumes/Data including all subdirectories to the localhost. This file is a config file used by the NFS system available under MacOS. I found the following blog article which basically has the solution + performance benchmarks in them:Įdit/Add the file /etc/exports and add the following line: /System/Volumes/Data -alldirs -mapall=501:20 localhost I can definitely recommend this whole series from LiveOverflow where he goes deeper into the whole namespacing topic and why linux docker containers are not VMs (if you are interested) And this “somehow” basically creates a whole lot of latency which reduces the performance dramatically. Therefore in Linux there is no difference between files on the host and container system but MacOS has to circumvent this feature “somehow”. This namespacing feature is present in the Linux kernel but MacOS is not based on Linux.

In Linux Docker basically “separates” all its containers via namespacing.

The Problemīasically Docker for MacOS doesn’t “mount” the filesystem of the container the same way as Linux does. You can also find many other tutorials online which seem to improve the performance but in my experience most of them didn’t. It has been known for a long time, that Docker has performance issues under MacOS. The following statements are how I interpreted the whole docker ecosystem and how I personally got a working docker environment with MacOS. Docker NFS Implementation for better performance in MacOS 11 (Big Sur)įirst of all: Docker in general is a very popular topic and has many ways how it can be used, configured and worked with.Gulp-Example for SCSS, JS and BrowserSync.React Library Example with multiple components.AMD, CJS, UMD, ESM – Modular JavaScript.Most important commands for a local repository.Free HTTPS certificate with Lets Encrypt.

Docker on mac performance