You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the vagrant box I have no permissionsin when I try to do a ls -la in the shared folder /vagrant_data
The output
When I vagrant upthe following happens vagrant up issue ==> default: Mounting shared folders...
If I vagrant ssh into the box and run ls -la in the shared folder the following error is produced: ls -la issue ls: cannot open directory .: Operation not permitted
Thanks for reporting this bug. I'm sure this was a real issue when originally reported (our fault for not looking sooner!) but there have been multiple Vagrant releases since the original report. I'm going to close this issue now and request you reopen the issue if you're still experiencing this problem. I'm sorry this wasn't looked at earlier ☹️
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Issue
In the vagrant box I have no permissionsin when I try to do a
ls -la
in the shared folder/vagrant_data
The output
vagrant up
the following happensvagrant up issue
==> default: Mounting shared folders...
vagrant ssh
into the box and runls -la
in the shared folder the following error is produced:ls -la issue
ls: cannot open directory .: Operation not permitted
Specifications
Vagrant version
Vagrant 1.8.1
Host operating system
Windows 10
VirtualBox
VirtualBox 5.0
Guest operating system
Ubuntu 14.04.4 LTS (GNU/Linux 3.13.0-79-generic i686)
Vagrantfile
most important lines in my vagrantfile
config.vm.synced_folder ".", "/home/vagrant/vagrant_data"
The
ls -la
differencesthe default vm (default vagrantfile)
the defective vm (my vagrantfile)
Similar issues
The text was updated successfully, but these errors were encountered: