If your dev documentation includes your devs running docker build, you're doing docker wrong.

The whole point is that you can build a working container image and then ship it to a registry (including private registries) so that your other developers/users/etc don't have to build them and can just run the existing image.

Then for development, you simply use a bind mount to ensure your local copy of the code is available in the container instead of the copy the container was built with.

That doesn't solve the performance issues on Windows and Mac, but it does prevent the "my environment is broke" issues that docker is designed to solve