Pascal de Vink
2018-09-19 07:46:26 UTC
Hi,
I'm running the latest version of macOS 10.14 public beta (which lags
behind the developer beta), and I'm running into problems using the latest
version of both Vagrant (2.1.5) and VirtualBox (5.2.18) and NFS sharing.
exist, and creating it manually also fails (both as regular user and root).
I've read up about it saw that the file is protected by the System
Integrity Protection. Using csrutil to disable it seems to work, so at
least I found a workaround.
However, I can not believe that would be the final solution, as that poses
a major security thread.
Is there anybody else that has the same problem, or can confirm that it has
been fixed in later developer betas?
--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+***@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/a73e00d9-7b15-4b60-9018-608012fbdc4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I'm running the latest version of macOS 10.14 public beta (which lags
behind the developer beta), and I'm running into problems using the latest
version of both Vagrant (2.1.5) and VirtualBox (5.2.18) and NFS sharing.
==> default: Exporting NFS shared folders...
==> default: Preparing to edit /etc/exports. Administrator privileges will
tee: /etc/exports: Operation not permitted
tee: /etc/exports: Operation not permitted
The nfsd service does not appear to be running.
Starting the nfsd service
==> default: Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
Looking into it further, it seems that /etc/exports doesn't currently==> default: Preparing to edit /etc/exports. Administrator privileges will
be required...
tee: /etc/exports: Operation not permittedtee: /etc/exports: Operation not permitted
tee: /etc/exports: Operation not permitted
The nfsd service does not appear to be running.
Starting the nfsd service
==> default: 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.254.1:/Users/<user>/<path> /vagrant
mount.nfs: Connection timed out
mount.nfs: Connection timed out
exist, and creating it manually also fails (both as regular user and root).
I've read up about it saw that the file is protected by the System
Integrity Protection. Using csrutil to disable it seems to work, so at
least I found a workaround.
However, I can not believe that would be the final solution, as that poses
a major security thread.
Is there anybody else that has the same problem, or can confirm that it has
been fixed in later developer betas?
--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+***@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/a73e00d9-7b15-4b60-9018-608012fbdc4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.