Can't access Local sites after setting up Vagrant

Hello,

I’ve set up Vagrant to run another local development environment on my Mac and now I can’t access my Local sites. There are no errors thrown by Local, but it takes a long time to get past the “Starting Local Machine”-phase.

This is my /etc/hosts/-file:

##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1	localhost
255.255.255.255	broadcasthost
::1             localhost 
fe80::1%lo0	localhost
185.27.174.169\tlocalhost



## vagrant-hostmanager-start id: 0ba93780-6f8d-4a38-bd4f-e642f3b4d346
192.168.50.5	spacial.dev

## vagrant-hostmanager-end

## vagrant-hostmanager-start id: 7f2300a4-f6bc-4fa2-967f-804a517120d8
192.168.50.5	trellis.dev
192.168.50.5	www.trellis.dev
## vagrant-hostmanager-end

## Local by Flywheel - Start ##
192.168.75.100 allan.dev #Local Site
192.168.75.100 gantry.dev #Local Site
192.168.75.100 grav.dev #Local Site
192.168.75.100 hitta.dev #Local Site
192.168.75.100 jgg.dev #Local Site
192.168.75.100 km.dev #Local Site
192.168.75.100 mosaic-beans.dev #Local Site
192.168.75.100 mosaic.dev #Local Site
192.168.75.100 rio.dev #Local Site
192.168.75.100 sincero.dev #Local Site
192.168.75.100 terapivakten.dev #Local Site
192.168.75.100 test.dev #Local Site
## Local by Flywheel - End ##

And this is my /etc/exports-file:

# VAGRANT-BEGIN: 501 5015210f-b5a8-42b6-a24b-f5f416537a05
"/Users/olafg/Dev/trellis.dev/site" 192.168.50.5 -alldirs -mapall=501:20
"/Users/olafg/Dev/trellis.dev/trellis" 192.168.50.5 -alldirs -mapall=501:20
# VAGRANT-END: 501 5015210f-b5a8-42b6-a24b-f5f416537a05
# Local by Flywheel NFS - Start #
/Users 192.168.75.100 -alldirs -mapall=501:20
# Local by Flywheel NFS - End #

Has anyone solved this issue previously?

Hi Olaf,

You may need to disable Faster Docker Volumes in Local.

Please see Local fails to start after reinstalling VirtualBox

We’re working on a solution to this NFS conflict issue.

I’m getting a similiar issue trying to use Local alongside a different NFS-using Vagrant project. My exports file looks like this, and because of the path collision, neither Local nor the other project will launch:

# VAGRANT-BEGIN: 501 51541f61-8280-4f93-bce3-cc305b9ad9fc
"/Users/matthewmcvickar/Sites/work/foobarbaz-project" 192.168.7.11 -alldirs -mapall=501:80
# VAGRANT-END: 501 51541f61-8280-4f93-bce3-cc305b9ad9fc
# Local by Flywheel NFS - Start #
/Users 192.168.95.100 -alldirs -mapall=501:20
# Local by Flywheel NFS - End # 

Is this the same issue?

I have that same issue. Took me forever to get Local set up b/c of this conflict with Trellis. At this point, I’m commenting out the Local export when using Trellis and vice versa.

Would be great to have a way to avoid these conflicts so we don’t need to touch our exports file.

Hey all,

Just wanted to let you know we’ve been testing an alternative to native NFS on macOS and the results are very promising.

Switching away from native NFS fixes this inherently.

I got round this (for now) by making my Local sites path something more specific: Instead of /Users, I’m using /Users/robrecord/Sites/Local and putting the Local sites in there. Hopefully it sticks, but for now it allows Vagrant to work.

It looks like it gets periodically reset.

@clay , could you please suggest to the team, simply using a more specific path instead of the incredibly general one used by Local?

Such as:

# Local by Flywheel NFS - Start #
~/Local Sites 192.168.95.100 -alldirs -mapall=501:20
# Local by Flywheel NFS - End #

Hi Rob,

Thanks for the suggestion!

Fortunately, we’re switching away from the built-in NFS in the upcoming version so it’ll fix that issue inherently. :smiley: