Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vagrant can't mount shared folder in VirtualBox 5.0.4 #7197

Closed
maguri opened this issue Apr 2, 2016 · 2 comments
Closed

Vagrant can't mount shared folder in VirtualBox 5.0.4 #7197

maguri opened this issue Apr 2, 2016 · 2 comments

Comments

@maguri
Copy link

maguri commented Apr 2, 2016

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

  • 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

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 differences

  • the default vm (default vagrantfile)

    vagrant@precise64:~$ ls -la
    total 48
    drwxr-xr-x 4 vagrant vagrant 4096 Sep 14 2012 .
    drwxr-xr-x 3 root root 4096 Sep 14 2012 ..
    -rw------- 1 vagrant vagrant 22 Sep 14 2012 .bash_history
    -rw-r--r-- 1 vagrant vagrant 220 Sep 14 2012 .bash_logout
    -rw-r--r-- 1 vagrant vagrant 3486 Sep 14 2012 .bashrc
    drwx------ 2 vagrant vagrant 4096 Sep 14 2012 .cache
    -rwxr-xr-x 1 vagrant vagrant 6487 Sep 14 2012 postinstall.sh
    -rw-r--r-- 1 vagrant vagrant 675 Sep 14 2012 .profile
    drwx------ 2 vagrant vagrant 4096 Apr 2 15:55 .ssh
    -rw-r--r-- 1 vagrant vagrant 0 Sep 14 2012 .sudo_as_admin_successful
    -rw------- 1 vagrant vagrant 6 Sep 14 2012 .vbox_version
    -rw------- 1 vagrant vagrant 12 Sep 14 2012 .veewee_version

  • the defective vm (my vagrantfile)

    vagrant@kalinge-vm:~$ ls -la
    total 32
    drwxr-xr-x 5 vagrant vagrant 4096 Apr 2 15:44 .
    drwxr-xr-x 4 root root 4096 Apr 2 15:43 ..
    -rw-r--r-- 1 vagrant vagrant 220 Apr 9 2014 .bash_logout
    -rw-r--r-- 1 vagrant vagrant 3637 Apr 9 2014 .bashrc
    drwx------ 2 vagrant vagrant 4096 Apr 2 15:43 .cache
    -rw-r--r-- 1 vagrant vagrant 675 Apr 9 2014 .profile
    drwx------ 2 vagrant vagrant 4096 Apr 2 15:43 .ssh
    drwxrwxrwx 1 vagrant vagrant 4096 Feb 28 22:42 vagrant_data

Similar issues

@chrisroberts
Copy link
Member

Hi there,

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 ☹️

Cheers!

@ghost
Copy link

ghost commented Apr 1, 2020

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.

@hashicorp hashicorp locked and limited conversation to collaborators Apr 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants