From 501f909deae0a71ea407323d516a379bbf6ce838 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Santiago=20Rodr=C3=ADguez?= Date: Wed, 31 Jan 2018 03:38:50 +0100 Subject: [PATCH] Add workaround for shared folders issue --- playbooks/archivematica/README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/playbooks/archivematica/README.md b/playbooks/archivematica/README.md index 6a0bebb8..d8cefd97 100644 --- a/playbooks/archivematica/README.md +++ b/playbooks/archivematica/README.md @@ -55,5 +55,10 @@ Deploy](docs/digital-ocean-install-example.rst) document. 6. The ansible playbook `singlenode.yml` specified in the Vagrantfile will provision using stable branches of archivematica. To provision using the qa 1.x/0.x branches, replace "vars-singlenode-1.6.yml" with "vars-singlenode-qa.yml" in `singlenode.yml`. You can also modify create a custom vars file and pass it instead (to modify role variables to deploy custom branches, etc.) +7. If you get errors regardig the Vagrant shared folders, they are usually due to different versions of Virtualbox. One way to fix it, is using a vagrant plugin that installs the host's Virtualbox Guest Additions on the guest system : + ``` + $ vagrant plugin install vagrant-vbguest + $ vagrant vbguest + ``` For more archivematica development information, see: https://wiki.archivematica.org/Getting_started