Open tylers-username opened 7 years ago
Actually, the first fail is at NFS detection. Installing with sudo apt-get install nfs-common nfs-kernel-server
and testing to see if the error continues to occur.
Edit: Because I assume that the error originally reported is a result of the box failing to launch, I am closing this ticket.
However, I continue to encounter the following error with NFS:
==> local: Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o vers=3,udp 192.168.47.1:/home/tyler/PhpStorm/Projects/Tyler/mage1box /var/www
result=$?
if test $result -eq 0; then
if test -x /sbin/initctl && command -v /sbin/init && /sbin/init 2>/dev/null --version | grep upstart; then
/sbin/initctl emit --no-wait vagrant-mounted MOUNTPOINT=/var/www
fi
else
exit $result
fi
Stdout from the command:
Stderr from the command:
mount.nfs: access denied by server while mounting 192.168.47.1:/home/tyler/PhpStorm/Projects/Tyler/mage1box
Fixing the NFS issue did not resolve the [Exception] String could not be parsed as XML
error. I assumed that Vagrant failing at NFS prevented the access to the Vagrant box causing the composer install to be executed on the host machine (I know, a stretch). But, of course, that was not the case.
My host is Ubuntu 17, but am experiencing the same on 16.10 and 16.04. My home directory is encrypted, but I am now deploying to an unencrypted directory.
Not sure what else I can provide from here.
Note: For anyone curious, the NFS issue was resolved by (1) deploying magestead in a non-encrypted directory and (2) by disabling NFS in the firewall.
After running
magestead new m1-base
with the options:I get the error shown below. The source of the problem appears to be that composer install is running on my host machine which has PHP 7 installed. If this is the case, my expectations are that the guest machine should be executing composer install.