Sequoia error prevents new site generation

Support
,
1

What issue or error are you experiencing?

This error stops me from creating any new sites on a fresh install of Sequoia:

Error: Error: spawn Unknown system error -86

at ChildProcess.spawn (node:internal/child_process:414:11)

at spawn (node:child_process:776:9)

at execFile (node:child_process:351:17)

at t. (node:electron/js2c/node_init:2:2610)

at /Applications/Local.app/Contents/Resources/app.asar/main/_helpers/execFilePromise.js:1:583

at new Promise ()

at Object. (/Applications/Local.app/Contents/Resources/app.asar/main/_helpers/execFilePromise.js:1:534)

at Generator.next ()

at /Applications/Local.app/Contents/Resources/app.asar/main/_helpers/execFilePromise.js:1:330

at new Promise ()

Followed by:
Local ran into a problem when trying to update the hosts file.

Please ensure that the hosts file is not locked by anti-virus

What steps can be taken to replicate the issue?

Feel free to include screenshots, videos, etc
Fresh install of Sequoia 15.0.1
Fresh install of Local Version 9.1.0+6719

System Details

  • Local Version:

  • Operating System (OS) and OS version:

Local Logs

Attach your Local Logs here (Help Doc - Retrieving Local’s Log)
local-lightning.log (12.1 KB)

Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

2

Hi @LosBenos

Rosetta 2 is required for Local’s Apple Silicon build due to the Nginx and MySQL Lighting Services compiled on the Intel architecture. We do plan to have a Local release out in the future that will drop this dependency but for now it is necessary.

You can install Rosetta by opening up a terminal window and using this command:

softwareupdate --install-rosetta

Others have found this doc to be helpful:

3

Thanks Nick…
That was an easy fix.
It might be a good idea to simply address the error message to be more informative while you’re developing the option to run without Rosetta.
Thanks all the same.
It’s all good now

4

Glad to hear things are working @LosBenos! That’s some good feedback regarding the error, but I believe we are close to having a Local release out that won’t need this. So hopefully it will be a non-issue soon!