Actually most problems here already described well in Docker docs: - https://docs.docker.com/storage/bind-mounts/#configure-mount-consistency-for-macos https:/

Actually most problems here already described well in Docker docs: - https://docs.docker.com/storage/bind-mounts/#configure-mount-consistency-for-macos https://docs.docker.com/storage/bind-mounts/#configure-mount... Due to it is being VM, contents are synced between host and VM. It takes time and damages IOPS greatly. Eg. Even running ~100MB Jar takes minutes... Side note that vim uses `swap` files `.$FILE.swp` when you write out, it removes the original file renames the temporary one to original one. So essentially inode or reference is different thats why it triggers sync with VM. Ed probably writes files in-place. Docker now uses inotify equalivent (fswatch?) on macOS, which is pretty much reliable than polling. Ofc if your app did not close file with exclusive read-write-lock, docker cannot do anything about it.