gunghogeoduck/osem-fcy
1
0
Fork 0
mirror of https://github.com/openSUSE/osem.git synced 2026-08-13 11:44:02 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix shared directory mounting on provisioning

Browse source 
Due to how the opensuse/openSUSE-42.1-x86_64 box is, there is no vagrant group
by default. When the shared folder is attemtped to mount, it fails with the
following

```
==> default: Mounting shared folders...
    default: /vagrant => /Users/kormoc/Projects/osem
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` vagrant /vagrant
mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g vagrant` vagrant /vagrant

The error output from the command was:

No such file or directory
```

This change will fix this issue to allow a single `vagrant up` to work correctly

To test this, you can run `vagrant destroy;vagrant up`. This will destroy your current environment and rebuild it from scratch.
This commit is contained in:
Rob Smith 2016-09-17 19:26:34 -07:00
parent 0dba45909f
commit 6f260d14fa
1 changed files with 11 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

11
Vagrantfile vendored
View file

@ -39,6 +39,17 @@ Vagrant.configure(2) do |config|
# argument is a set of non-required options.
# config.vm.synced_folder "../data", "/vagrant_data"
# When using the default settings, we will attempt to mount this share
# as the vagrant user and the vagrant group. Alas, box opensuse/openSUSE-42.1-x86_64
# does not have the vagrant group created, so this share fails and
# requires manual mounting for the vagrant setup to continue. Setting
# to the hardcoded numbers will allow the mount to successfully
# mount without working about the group mismatch
VAGRANT_UID = 1000 # User vagrant
VAGRANT_GID = 100 # Group users
config.vm.synced_folder ".", "/vagrant",
owner: VAGRANT_UID, group: VAGRANT_GID
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox: