I am experiencing an issue that has come up before here in the forums, but I feel like I’ve tried every possible suggested solution - both here on the discourse, github and stack overflow - but to no avail. My setup: macOS Sierra (10.12.2) Vagrant 1.9.1 Ansible 2.2.0.0 I’ve followed every step of…

FYI, I discovered that using using docker-machine + docker-machine-nfs (which also are powered by VirtualBox) will cause an NFS exports collision. The solution I found for now was to comment out the exports from docker-machine while using Trellis.

I ran into this issue again today. I spun up on older project and was met with the mounting NFS shared folders issue. Prior to spinning up the old project, I was working on a few other projects flawlessly. Now that the old project spit the error, I’m having a really hard time getting my other proje…

It turns out that somehow my Mac encountered Kernel Panic and had suffered from disk permissions. So far, after the fix, I’ve been able to boot up vagrant boxes just fine (without any NFS errors) but I still can’t get them to assign the correct IP I’ve given them in their vagrant host files. Loading…

Now I’m working on getting a totally different project up and running. I was able to ‘vagrant up --provision’ successfully but could not get the project to load in the browser. It just thinks. So I went a head and destroyed it and ran ‘vagrant up --provision’ again and now this project is throwing …

[image] joshb: One thing I noticed is that my /etc/hosts file is using the same IP address (192.168.50.5) for each project I attempt to launch regardless of the IP address I’ve defined in the trellis hosts files for local development. You need to define it here, too: roots/trellis/bl…

Thanks Ben. I actually realized that this morning, that I’ve been defining it in the wrong place Regardless, I’m still struggling with NFS issues today. Can’t seem to get them sorted out. Since I’ve destroyed all my boxes, I’m wondering if it would help to completely uninstall VirtualBox, Vagrant, A…

If you destroy the boxes, delete the .vagrant directories, clear out any relevant entries in /etc/exports, then update the IPs to be unique in vagrant.default.yml, then everything should be fine if you just provision again

I’ve destroyed all boxes and deleted .vagrant on one project and cleared out my exports. Running vagrant up --provision still gives me the following error: The nfsd service does not appear to be running. /bin/launchctl exited with status 3 ==> default: Mounting NFS shared folders... The following S…

After updating to Mojave, my Full Disk Access option has returned. I was able to successfully boot up 3 different boxes with different IPs. All of them were loading in my browser at the same time. I went to boot up a 4th box but it was hanging at some point, probably due to low memory issues. I can…

Vagrant up fails on mounting NFS shared folders

trellis

bluemooninc December 30, 2019, 12:58am 35

If you use Mojav or Catalina. Take a look this link.

1 Like

Provisioning Development requests sudo, gives /bin/sh: lsb_release: command not found