i never tried this but i think it's similar to docker-sync, where you still have to modify your docker compose files. it's not good for people who want a single consistent docker-compose file that would work across varying distributions (ie; opensource project).
These options are part of the Docker API and the underlying engine implements it as needed. On Linux hosts there is nothing to tweak as bind mounts offer full consistency without compromising performance.
In Docker for Mac it tweaks the consistency settings for mounts that cross the VM barrier with osxfs.
So itnisnsafe to define these in any comoose file no matter where it runs, just need to make sure that the app in the container can actually deal with the consistency level applied to the particular mount.
Newer versions of docker have been much better, but now it just eats up a ton of ram. The ram setting in prefs doesn’t seem to actually limit it at all.
but using Dinghy greatly helped sped everything up due to it using nfs. just in case anyone wanted to know.