Within the VM, the /vagrant directory (or /home/vagrant in your particular case) is mounted as vboxsf file system (and not ext2). Sometimes read/write of specific files will produce errors. I encountered this as well when trying to read VMDK files from shared folders.
On Thursday, 16 April 2020 04:38:48 UTC-4, Fernando Estrella wrote: > > Hello > > Yesterday I was working with Vagrant. I work with a team and I wanted the > folder that vagrant opened into (/home/vagrant) when doing ssh to be the > folder that would sync with the Vagrant folder in the host computer (where > the Vagrantfile is) as opposed to it syncing in the /vagrant folder in the > guest, so that they wouldn't have to move through folders so much. So I > added another line to the Vagrantfile so achieve this. The thing is that > when I ran with "npm install", it would install many things in the home > folder, which now was syncing between the host and the guest, and that gave > an error that was very hard to debug (it mentioned something like ENOENT > and that a file could not be reached - sometimes different files would be > mentioned - among others). Apparently when syncing it locks some files and > npm install couldn't complete. > > So my suggestion is to either make a note of this in the comments in the > Vagrantfile, or on the website, or I don't know, whatever you guys suggest. > > Thanks! > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/2612f2a2-a5f5-4e7a-b25f-b22b5f135f09%40googlegroups.com.