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

Cannot use links for resource folders #113

Closed
kghmanuel opened this issue Jun 14, 2017 · 2 comments
Closed

Cannot use links for resource folders #113

kghmanuel opened this issue Jun 14, 2017 · 2 comments
Assignees
Labels
Milestone

Comments

@kghmanuel
Copy link

Given:

  1. windows OS
  2. D:\opt\vagrant is a link/junction to another folder, e.g. vagrant [D:\Vanguard\code\mlvagrant\opt\vagrant]
  3. D:\space\installers is a link/junction to another folder, e.g. software [D:\installers]
  • link/junction created using mklink /J command

Encountered the following error:

D:\VMs\democat>vagrant up --no-provision
==> democat-ml1: Mounting shared folders...
    democat-ml1: /vagrant => D:/VMs/democat
    democat-ml1: /opt/vagrant => D:/opt/vagrant
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attemped was:
 
set -e
mount -t vboxsf -o uid=`id -u vagrant`,gid=`getent group vagrant | cut -d: -f3` opt_vagrant /opt/vagrant
mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g vagrant` opt_vagrant /opt/vagrant
 
The error output from the command was:
 
/sbin/mount.vboxsf: mounting failed with the error: Invalid argument
@grtjn
Copy link
Owner

grtjn commented Jun 15, 2017

There are two issues going on here:

  • Vagrant was unable to mount VirtualBox shared folders.
  • Use of link/junction (created using mklink /J command)

The first is an issue with VBox itself. Upgrade to 5.2.14 seems to help.

The latter unfortunately simply doesn't seem to work with Vagrant/VBox.

@grtjn
Copy link
Owner

grtjn commented Jun 15, 2017

Got offline confirmation that 5.2.14 worked. And don't link folders you'd like to mount on Windows, move or copy your files instead..

@grtjn grtjn closed this as completed Jun 15, 2017
@grtjn grtjn self-assigned this Jun 15, 2017
@grtjn grtjn added this to the 1.0.5 milestone Jun 15, 2017
@grtjn grtjn added the bug label Jun 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants