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
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 attempted was:
mount -t vboxsf -o uid=1000,gid=1000,_netdev vagrant /vagrant
The error output from the command was:
: No such device
The text was updated successfully, but these errors were encountered:
Please follow the issue template instead of your own format when filing a bug report; this reduces the time and effort needed to resolve your problem.
The following error message seems to already address that this is normally NOT a Vagrant issue but an issue within the Vagrant box(VM image) you're trying to use:
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.
Have you verified that the Vagrant box you're using has satisfied this requirement yet? Please provide a minimal Vagrantfile bug reproducer(along with other fields demanded by the issue template, whenever applicable) to help troubleshoot your problem.
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 attempted was:
mount -t vboxsf -o uid=1000,gid=1000,_netdev vagrant /vagrant
The error output from the command was:
: No such device
The text was updated successfully, but these errors were encountered: