Installation blocked at third step (Local Image)

Hi,

after a long story of difficult launches of Local (throughout different versions up to 2.0.6), i decided to throw it all (Local and VirtualBox) and reinstall it all over (all my sites have of course been exported and my Blueprints archived before).

I followed the instructions described on that topic : How do I uninstall Local on macOS? - FAQ - Local Community

To be noted: VirtualBox has been on my MacBook Pro before Pressmatic and then Local as i’ve been testing the roots.io stack (Trellis, Bedrock, and Sage) at /Users/xxx/roots-test1.com.
Related to that, i deleted its references in the hosts file and trashed the folders and files as didn’t need them anymore.

Once everything has been uninstalled, i reinstalled Local 2.0.8 in Applications. At launch, the 2 first steps (VirtualBox and Host Machine) are done, but the third step is not starting:

While waiting, i checked the Local log file to find that, if i understand things in that log, the launch process stumbled on finding that roots-test1.com site:

Sep 27, 2017, 8:17 AM GMT+2 - info: [main/docker-machine-nfs] Enabling Docker Machine NFS
Sep 27, 2017, 8:17 AM GMT+2 - warn: [main/index] Unhandled Rejection at: Promise Promise {
{ error:
{ Error: Command failed: /usr/bin/sudo -n -E – sh “/Applications/Local by Flywheel.app/Contents/Resources/extraResources/shell-scripts/nfs-configure-mac.sh” “192.168.92.100” “501” “20”
exports:2: path contains non-directory or non-existent components: /Users/vincentp/_PRO/vpell/tests/wordpress_dev/roots-test1.com/site
exports:2: no usable directories in export entry
exports:2: using fallback (marked offline): /
exports:5: /Users conflicts with existing export /Users/vincentp/_PRO/vpell/tests/wordpress_dev/roots-test1.com/site
at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
killed: false,
code: 4,
signal: null,
cmd: ‘/usr/bin/sudo -n -E – sh “/Applications/Local by Flywheel.app/Contents/Resources/extraResources/shell-scripts/nfs-configure-mac.sh” “192.168.92.100” “501” “20”’ },
stdout: ‘Configuring /etc/exports on macOS\nThe nfsd service is already enabled.\n’,
stderr: ‘exports:2: path contains non-directory or non-existent components: /Users/vincentp/_PRO/vpell/tests/wordpress_dev/roots-test1.com/site\nexports:2: no usable directories in export entry\nexports:2: using fallback (marked offline): /\nexports:5: /Users conflicts with existing export /Users/vincentp/_PRO/vpell/tests/wordpress_dev/roots-test1.com/site\n’,
exitCode: 4 } } reason:
{ error:
{ killed: false,
code: 4,
signal: null,
cmd: ‘/usr/bin/sudo -n -E – sh “/Applications/Local by Flywheel.app/Contents/Resources/extraResources/shell-scripts/nfs-configure-mac.sh” “192.168.92.100” “501” “20”’ },
stdout: ‘Configuring /etc/exports on macOS\nThe nfsd service is already enabled.\n’,
stderr: ‘exports:2: path contains non-directory or non-existent components: /Users/vincentp/_PRO/vpell/tests/wordpress_dev/roots-test1.com/site\nexports:2: no usable directories in export entry\nexports:2: using fallback (marked offline): /\nexports:5: /Users conflicts with existing export /Users/vincentp/_PRO/vpell/tests/wordpress_dev/roots-test1.com/site\n’,
exitCode: 4 }

I guess i didn’t erase/delete somewhere a reference to that access path, but i don’t know where and how to do that. Or my understanding of things is completely wrong :wink:

Anyway, i’m stuck here and need somebody’s help as i can’t access anymore my sites and blueprints. :frowning_face:

Hi @vpell,

Sorry for the trouble!

You can remove the conflicting NFS exports by opening Terminal and running sudo nano /etc/exports

If you don’t want to go that route, you can disable Faster Docker Volumes by doing the following:

  1. Browse to ~/Library/Application Support/Local by Flywheel in Finder. You can get there easily by pressing Cmd + Shift + G.
  2. Create a file named nfs.json containing { disabled: true }
  3. Relaunch Local

Thank for the quick reply.

I went for the first option (as i do not want to disable a feature with “Faster” in its name :wink: ), but was overconfident about my capabilities :wink:
What part should i remove in the file (line 2, lines 1-3, anything else) ?
Here is the content of the file:

# VAGRANT-BEGIN: 501 fb0bac16-1cbf-4704-8590-d88aa12f1c65
“/Users/vincentp/_PRO/vpell/tests/wordpress_dev/roots-test1.com/site” 192.168.50.5 -$
# VAGRANT-END: 501 fb0bac16-1cbf-4704-8590-d88aa12f1c65
# Local by Flywheel NFS - Start #
/Users 192.168.92.100 -alldirs -mapall=501:20
# Local by Flywheel NFS - End #

Feel free to remove everything in the file. :slight_smile:

If you’re still using the roots-test1.com site and start it up, it may add it back to /etc/exports. If that’s the case then you’ll want to disable NFS if the Vagrantfile for that site.

Ok, thanks.

One last round of questions, so that i learn something today:

  1. What does this “Faster Docker Volumes” feature? What will i lose by disabling it?
  2. If i delete everything in that file, does it disable the “Faster Docker Volumes” feature?
  3. I don’t use the roots-test1.com anymore. In that context, if i still want the “Faster Docker Volumes” feature, but get rid of my problem, what should i remove from the file? My guess would be to remove the lines 1 to 3. Correct?
  1. Faster Docker Volumes enables NFS instead of VirtualBox shared folders. You should see a noticeable speed increase with it enabled.
  2. Kind of. Local will attempt to re-add its lines the next time you open Local if it’s not disabled.
  3. Yup!

Let’s do that!
I’ll get get back here to tell you how it went.
Thanks for your time and explanations.

1 Like

@clay
Install process is completed and the launches problems i had disappeared.
Thanks for your help.

1 Like

Awesome, glad to hear!