-
-
Notifications
You must be signed in to change notification settings - Fork 646
Drupalvm sync folder not showing on host machine #734
Comments
The only difference between my environments (Windows 10 / Mac OS X 10.11) and yours seems to be that I have Vagrant 1.8.1, while you have 1.8.3. Over in #683 you had shown that the synced dir seems to not be created, so I'm thinking we can maybe test some more troubleshooting to see where exactly that directory is being generated! Inside the VM, can you run |
I ran that command and this is the output. unfortunately my linux skills are not there yet sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
|
inside the vm i ram mount drupalvm from the /var/www directory and i get this error could that be it
|
@mooru no, it looks like there's a mount for the /vagrant directory at least—see:
But there's no mount for the Can you delete your |
OK. i will try that and see
|
I have deleted the config.yml file, duplicated it again and vagrant provision and it didn't work. i also ran vagrant provision with the default.config.yml and it still didn't work |
+1 |
@mooru if you have a box provisioned already could you run the following and post that massive debug dump that vagrant outputs: vagrant halt
vagrant up --debug Edit: actually it seems this gives enough output (and a lot less than vagrant halt
VAGRANT_LOG=info vagrant up If it helps I'm specifically interested in what comes after This is my own output:
|
I ran vagrant up --debug and this is the output ==> drupalvm: Exporting NFS shared folders... |
Looks correct so far. After you input the password, what follows? I'm looking for these: and
|
I can reproduce this error with default config.yml file (local_path ".") Here is my vagrant up --debug:
The problem seems to be in "can't find /var/www/drupalvm in /etc/fstab" If I manually try to mount it in vagrant I get the same error, so it looks the /etc/fstab wasn't updated with this mount config entry. |
The commit that got merged is hashicorp/vagrant@61d2a50. Maybe this is a Vagrant 1.8.3+ issue. I'll update vagrant on my own laptop and see if i can reproduce it. |
Also compare
to mine
|
@alesrebec it's a long shot but could you try with adding mount_options: ['vers=3', 'udp'] to your synced folder: vagrant_synced_folders:
# The first synced folder will be used for the default Drupal installation, if
# any of the build_* settings are 'true'. By default the folder is set to
# the drupal-vm folder.
- local_path: .
destination: /var/www/drupalvm
type: nfs
create: true
mount_options: ['vers=3', 'udp'] |
Actually that might be it. I'm thinking this commit caused an issue when the |
So should we downgrade to vagrant 1.8.1 for it to work
|
Try adding a vagrant_synced_folders:
# The first synced folder will be used for the default Drupal installation, if
# any of the build_* settings are 'true'. By default the folder is set to
# the drupal-vm folder.
- local_path: .
destination: /var/www/drupalvm
type: nfs
create: true
mount_options: ['vers=3', 'udp'] If that's the bug, it should work as long as I'll update Vagrant locally in a bit to see if I can reproduce it. |
Hmm setting the mount_options didn't help but I found another fix. Before:
After defaulting
|
…folders with empty mount_options
@mooru @alesrebec could you try out the PR above and test if it solves the problem for you. |
@oxyc I can confirm that "drupal" directory is now created in local_path ".".
|
@alesrebec great! That should be fixed in master already #726. |
I tried do a fresh vagrant uo after destroying the VM files. i added mount_options: [] i can now see the drupal folder but for some reason i get errors when it get to composer install with vagrant provosion TASK [Generate Drupal project with composer package.] ************************** PLAY RECAP ********************************************************************* Ansible failed to complete successfully. Any error output should be |
You should set I'm wondering if the error happened because of all the failures before. Could you try: # This directory shouldn't exist before the provision takes place.
rm -r /Users/martinoru/Sites/drupal8/drupal
# Re-build from scratch.
vagrant destroy -f
vagrant up |
Still getting this error after doing all TASK [Generate Drupal project with composer package.] ************************** |
I expected the same problem and the PR #737 fixes it. The folder get mounted as defined. Vagrant 1.8.4 |
It is working well now. I guess the mount_options solved it |
As I tried the mount_options before, it doesn't work. But now I tried it again and it works also for me. |
I'm testing #737 with 1.8.1 to make sure it doesn't cause any regressions. Once that's done I'll merge, and do a new bugfix release so this issue gets resolved. Vagrant update issues-- |
Issue #734: Fix Vagrant 1.8.4 failing to mount NFS synced folders with empty mount_options
To all in this issue—please try with the latest |
This should be fixed with the latest release, 3.1.2 |
I have done 2 installs of drupalvm from the git clone but the sync folder has not shown up for either installations (ie under /Users/me/Sites/drupalvm/drupal)
vagrant version 1.8.3
Virtualbox version 5.0.20
MacOSX 10.11.5
I also didn't changed the config.yml file
I have done a second vagrant destroy and vagrant up still no changes. when i do vagrant ssh i can see the drupal files installed.
The text was updated successfully, but these errors were encountered: