Following installation instructions verbatim fails on Linux

[dandv]

Just ran the yarn install; yarn start commands on a fresh Ubuntu 22.04 installation:

$ yarn install
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning "@docusaurus/core > [email protected]" has unmet peer dependency "react-loadable@*".
warning "@docusaurus/core > react-dev-utils > [email protected]" has unmet peer dependency "typescript@>= 2.7".
warning "@docusaurus/preset-classic > @docusaurus/theme-search-algolia > @docsearch/react > @algolia/[email protected]" has unmet peer dependency "@algolia/client-search@>= 4.9.1 < 6".
warning "docusaurus-plugin-sass > [email protected]" has unmet peer dependency "webpack@^4.36.0 || ^5.0.0".
warning " > [email protected]" has incorrect peer dependency "react@^0.14.0 || ^15.0.0".
warning "netlify-cli > @netlify/build > [email protected]" has unmet peer dependency "@types/node@*".
[5/5] Building fresh packages...
[1/5] ⠂ core-js-pure
[2/5] ⠂ core-js
[3/5] ⠂ @netlify/esbuild
[4/5] ⠂ unix-dgram
error ~/weaviate-io/node_modules/core-js: Command failed.
Exit code: 1
Command: node -e "try{require('./postinstall')}catch(e){}"
Arguments: 




warning Error running install script for optional dependency: "~/weaviate-io/node_modules/unix-dgram: Command failed.
Exit code: 1
Command: node-gyp rebuild
Arguments:
Directory: ~/weaviate-io/node_modules/unix-dgram
Output:
Error: no suitable /tmp/yarn--1675932502224-0.40481357652144667/node executable found"
info This module is OPTIONAL, you can safely ignore this error

$ yarn start
yarn run v1.22.19
$ docusaurus start
Error: no suitable /tmp/yarn--1675932625012-0.7926456314193209/node executable found
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Fortunately npm start worked, but we should improve the DX here, ideally supporting the standard npm install; npm start flow (see #424).

[databyjp]

Hi @dandv I’m assigning this to the backlog for now. But if there’s an easy fix we can implement it.

[dandv]

yarn install; yarn start works fine now on Fedora. I think we can close.