Since I'm rebuilding the Linux kernel on a daily basis, having the kernel source checked out inside a Docker container (in my kernel cross-compile Docker environment) for compile time speed is essential.īut getting access to those files from my preferred IDE (Sublime Text) on my Mac host system is well nigh impossible.

If you're on Linux, all this extra complexity isn't needed-you could just mount a volume from your local filesystem at full speed.īut why don't you just run Linux, then, Jeff? Yeah. What finally forced me to come up with a better 'reverse volume' solution was the fact that my macOS APFS filesystem is not case sensitive, meaning working with large codebases like the Linux kernel source tree is infeasible inside my main Mac filesystem (due to it having files with the same name, just different casing). This is because the virtualized filesystem, which used osxfs for a while and will soon be upgraded to use VirtioFS.īut if you need to do large operations on huge codebases inside a shared directory, even using NFS to share from the Mac into Docker is a lot slower than running a native Docker volume or just using files inside the container's own filesystem.

For years, Mac users have dealt with slow filesystem performance for Docker volumes when using Docker for Mac.

Cross compile for mac on linux