5

I know there are multiple threads discussing NFS mounted volumes and file modification watch issues. Since most of the discussions are old, some from 8 years ago, my goal here is to compile some and bring them up again to check what are the most recent solutions you guys have been using to handle those issues.

The core problem
Linux relies on inotify, a kernel subsystem, to generate events when files are modified (changed/deleted) and those events are most often used by developer tools to watch files to trigger some task. The core issue is that when you have a volume/folder shared via NFS protocol, it doesn't generate the events, and therefore the tools need to use polling methods instead of trigger based on events.

Polling methods often create multiple issues such as high CPU usage, delay to trigger tasks over file alterations, and so on.

Some of the watching tools:

Popular threads

Nice solution attempts

My current challenge
We run our dev env using macOS as host, Vagrant (provider Virtualbox) with Alpine Linux as the guest, and Docker containers for the services (Node, NGINX...), the setup is running smoothly for everything aside from when the frontend developers need to watch file modifications using webpack watch feature. It works with polling but with a delay of 3-10 seconds.

Any updates or any recommendations on how you solve this problem?

brngyn
  • 96
  • 6
  • thank you for compiling this. have you found anything more on this since you posted? i'm currently running into this situation. – Switch386 Oct 20 '22 at 21:18
  • 1
    @Switch386 - I don't work with this environment for a long time now. I have been dealing with Docker only. However, I must say that sometime after the compilation of this I was able to make the [https://github.com/adrienkohlbecker/vagrant-fsnotify](vagrant-fsnotify) work fine and consistently. Give it a try. – brngyn Oct 22 '22 at 03:31

1 Answers1

0

I've been able to work around this issue by setting the actimeo NFS option to 1. This reduces the length of time that NFS caches the file system attributes which seems to keep the host and guest in near sync. Webpack watch now picks up changes for me almost immediately.

Here is the VagrantFile setting I use to implement this NFS share. Note the mount_options setting

config.vm.synced_folder "./my_host_syncd_folder", "/guest/path", type: 'nfs', mount_options: ['actimeo=1']
MatthewT
  • 1
  • 3