-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wp-env causes segmentation fault on Ubuntu 20.04 #22731
Comments
🤔
Out of curiosity, did you try updating
A quick google seemed to indicate this is a really common problem when running Docker in Linux environments. Do you think there is anything we can do to mitigate it on our side of things? It sounds like fixing it would have to do with the local docker engine install. We could add docs to talk about how to fix it if you find a solution (https://askubuntu.com/questions/477551/how-can-i-use-docker-without-sudo) |
@sainthkh I'm running things just fine, on Ubuntu 20.04 with NVM, when I add wp-env to my project's package.json, scripts section. I haven't attempted the use of NPX. What version of Node & NPM are you using with your setup? I've tested this is working with both v10 & v12 of Node. |
I'll also add that I have also been able to run wp-env fine on PopOS, which is based on Ubuntu. |
Following the setting from #25060, it works. Close this issue. |
I'd like to note that I recently setup a new laptop running KDE Neon (which is based on Ubuntu), and following the steps detailed in the latest version of the docs worked for me: |
Describe the bug
When you run
npx wp-env start
, you got the message,When you run
sudo npx wp-env start
, you got the message,To reproduce
Steps to reproduce the behavior:
npm i
.npx wp-env start
orsudo npx wp-env start
.It might not be reproducible because it's related with nodejs version and compiling system.
Expected behavior
wp-env
executes correctly.Screenshots
N/A
Editor version (please complete the following information):
Desktop (please complete the following information):
Smartphone (please complete the following information):
N/A
The text was updated successfully, but these errors were encountered: