You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some reason, Apple Silicon based Macs error out during docker-build of the backend.
Based off some research on Stack Overflow it seems to have something to do with M1 chip support for the node-gyp package.
To reproduce
Steps to reproduce the behavior:
Follow dev guide as normal on Apple Silicon powered Mac
Run NPM start
docker compose will error out in backend 6/7
Expected behavior
What did you expect to happen that didn't?
To run XFD on local host
Any helpful log output or screenshots
Paste the results here:
> [backend 6/7] RUN PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true npm ci:5.488 npm WARN deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.5.530 npm WARN deprecated [email protected]: Use your platform's native performance.now() and performance.timeOrigin.5.915 npm WARN deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.8.244 npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.17.55 npm WARN deprecated @aws-sdk/[email protected]: This package has moved to @smithy/util-retry17.59 npm WARN deprecated @aws-sdk/[email protected]: This package has moved to @smithy/smithy-client17.62 npm WARN deprecated @aws-sdk/[email protected]: This package has moved to @smithy/node-config-provider18.11 npm WARN deprecated @aws-sdk/[email protected]: This package has moved to @smithy/config-resolver22.51 npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.32.74 npm notice 32.74 npm notice New major version of npm available! 9.9.3 -> 10.5.032.74 npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.5.0>32.74 npm notice Run `npm install -g [email protected]` to update!32.74 npm notice 32.75 npm ERR! code 132.75 npm ERR! path /app/node_modules/bufferutil32.76 npm ERR! command failed32.76 npm ERR! command sh -c node-gyp-build32.76 npm ERR! gyp info it worked if it ends with ok32.76 npm ERR! gyp info using [email protected]32.76 npm ERR! gyp info using [email protected] | linux | arm6432.76 npm ERR! gyp ERR! find Python 32.76 npm ERR! gyp ERR! find Python Python is not set from command line or npm configuration32.76 npm ERR! gyp ERR! find Python Python is not set from environment variable PYTHON32.76 npm ERR! gyp ERR! find Python checking if "python3" can be used32.76 npm ERR! gyp ERR! find Python - "python3" is not in PATH or produced an error32.76 npm ERR! gyp ERR! find Python checking if "python" can be used32.76 npm ERR! gyp ERR! find Python - "python" is not in PATH or produced an error32.76 npm ERR! gyp ERR! find Python 32.76 npm ERR! gyp ERR! find Python **********************************************************32.76 npm ERR! gyp ERR! find Python You need to install the latest version of Python.32.76 npm ERR! gyp ERR! find Python Node-gyp should be able to find and use Python. If not,32.76 npm ERR! gyp ERR! find Python you can try one of the following options:32.76 npm ERR! gyp ERR! find Python - Use the switch --python="/path/to/pythonexecutable"32.76 npm ERR! gyp ERR! find Python (accepted by both node-gyp and npm)32.76 npm ERR! gyp ERR! find Python - Set the environment variable PYTHON32.76 npm ERR! gyp ERR! find Python - Set the npm configuration variable python:32.76 npm ERR! gyp ERR! find Python npm config set python "/path/to/pythonexecutable"32.76 npm ERR! gyp ERR! find Python For more information consult the documentation at:32.76 npm ERR! gyp ERR! find Python https://github.com/nodejs/node-gyp#installation32.76 npm ERR! gyp ERR! find Python **********************************************************32.76 npm ERR! gyp ERR! find Python 32.76 npm ERR! gyp ERR! configure error 32.76 npm ERR! gyp ERR! stack Error: Could not find any Python installation to use32.76 npm ERR! gyp ERR! stack at PythonFinder.fail (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:330:47)32.76 npm ERR! gyp ERR! stack at PythonFinder.runChecks (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:159:21)32.76 npm ERR! gyp ERR! stack at PythonFinder.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:202:16)32.76 npm ERR! gyp ERR! stack at PythonFinder.execFileCallback (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:294:16)32.76 npm ERR! gyp ERR! stack at exithandler (node:child_process:430:5)32.76 npm ERR! gyp ERR! stack at ChildProcess.errorhandler (node:child_process:442:5)32.76 npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:517:28)32.76 npm ERR! gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:290:12)32.76 npm ERR! gyp ERR! stack at onErrorNT (node:internal/child_process:477:16)32.76 npm ERR! gyp ERR! stack at process.processTicksAndRejections (node:internal/process/task_queues:82:21)32.76 npm ERR! gyp ERR! System Linux 6.6.16-linuxkit32.76 npm ERR! gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"32.76 npm ERR! gyp ERR! cwd /app/node_modules/bufferutil32.76 npm ERR! gyp ERR! node -v v18.19.032.76 npm ERR! gyp ERR! node-gyp -v v9.4.132.76 npm ERR! gyp ERR! not ok32.77 32.77 npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-03-15T17_20_57_413Z-debug-0.log
Add any screenshots of the problem here.
The text was updated successfully, but these errors were encountered:
🐛 Summary
What's wrong? Please be specific.
For some reason, Apple Silicon based Macs error out during docker-build of the backend.
Based off some research on Stack Overflow it seems to have something to do with M1 chip support for the node-gyp package.
To reproduce
Steps to reproduce the behavior:
Expected behavior
What did you expect to happen that didn't?
To run XFD on local host
Any helpful log output or screenshots
Paste the results here:
Add any screenshots of the problem here.
The text was updated successfully, but these errors were encountered: