I'm working on Mac (Mojave) and using Vagrant for local dev. server. "nfs" is set to true if that maters. On vagrant box I run Ubuntu 18.04. Drupal version is 8.7.2.

I add some new image field to some existing content type. For that field I set directory name, where files should be stored, i.e. "people" so dir is created in sites/default/file.

Then when I edit some node in that type and upload image for the first time it works fine. But when I edit another one I can not upload image - this directory becomes write protected?! And then when I manually allow writing (change dir permissions) I can upload image again and it works well after that for all other nodes.

So it's like after first upload Drupal makes directory write protected for some reason?! Or is that done by virtual box?

Any idea why is that happening?

I'm working on Mac (Mojave) and using Vagrant for local dev. server. "nfs" is set to true if that maters. On Vagrant box I run Ubuntu 18.04. Drupal version is 8.7.2.

I add some new image field to some existing content type. For that field I set directory name, where files should be stored, i.e. "people" so dir is created in sites/default/file.

Then when I edit some node in that type and upload image for the first time it works fine. But when I edit another one I can not upload image - this directory becomes write protected?! And then when I manually allow writing (change dir permissions) I can upload image again and it works well after that for all other nodes.

So it's like after first upload Drupal makes directory write protected for some reason?! Or is that done by virtual box?

Any idea why is that happening?