[wp-trac] [WordPress Trac] #55914: npm install still does not work on wordpress-trunk on new Mac M1's (Unknown MySQL server host 'mysql')
WordPress Trac
noreply at wordpress.org
Fri Jun 3 21:51:56 UTC 2022
#55914: npm install still does not work on wordpress-trunk on new Mac M1's (Unknown
MySQL server host 'mysql')
------------------------------+-----------------------------
Reporter: sandrasanzdev | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Build/Test Tools | Version: trunk
Severity: normal | Keywords: needs-patch
Focuses: |
------------------------------+-----------------------------
This is a follow-up to #52356.
When running `npm run env:install` I get this error, and need to manually
change the mysql image to `amd64/mariadb` in the docker-compose.yml file
to get it to work. I know this happened at least to another person with an
M1 besides me on WCEUs contributor day.
{{{
> WordPress at 6.1.0 env:install
> node ./tools/local-env/scripts/install.js
Creating network "wordpress-develop_wpdevnet" with driver "bridge"
Creating wordpress-develop_cli_run ... done
ERROR 2005 (HY000): Unknown MySQL server host 'mysql' (-2)
ERROR: 1
node:child_process:902
throw err;
^
Error: Command failed: docker-compose run --rm cli config create
--dbname=wordpress_develop --dbuser=root --dbpass=password --dbhost=mysql
--path=/var/www/src --force
at checkExecSyncError (node:child_process:828:11)
at execSync (node:child_process:899:15)
at wp_cli (/Users/sandra/Projects/WCEU/ContributorDay/wordpress-
develop/tools/local-env/scripts/install.js:52:2)
at Object.<anonymous> (/Users/sandra/Projects/WCEU/ContributorDay
/wordpress-develop/tools/local-env/scripts/install.js:14:1)
at Module._compile (node:internal/modules/cjs/loader:1105:14)
at Object.Module._extensions..js
(node:internal/modules/cjs/loader:1159:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Function.executeUserEntryPoint [as runMain]
(node:internal/modules/run_main:77:12) {
status: 1,
signal: null,
output: [ null, null, null ],
pid: 3097,
stdout: null,
stderr: null
}
}}}
It's weird because it seems that this was a known issue that was already
patched, and the fix seemed to work for some people.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/55914>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list