Env: Access denied for user 'username_here'@'X.X.X.X' error running wp-env start.

[StevenDufresne]

Description

When trying to start a new environment using wp-env, the CLI issues the following error:

mysqlcheck: Got error: 1045: Access denied for user 'username_here'@'172.18.0.5' (using password: YES) when trying to connect

This issue is not specific to working locally using this repository, but exists wherever @wordpress/env is used.

Step-by-step reproduction instructions

1. Destroy your local environment npm run wp-env destroy
2. Re-provision: npm run wp-env start

Expect to see the errors. Should you not see the error, make sure your docker images are updated to the latest.

Quick Debugging

• username_here was implemented in the WordPress docker image fairly recently (docker-library/wordpress@8f5bcc1#diff-7f28a0f62019f2d8b061638e8c3aea207404c1499f1c9241db3216fadd8f4530)
• the wp-config.php in the WordPress container matches the default config in the PR listed above.
• the wp-config.php includes the getenv_docker function that looks for a local env_FILE that does not exist in the WordPress container.
• When looking at the container using the docker desktop app, I see No 'wp-config.php' found in /var/www/html, but 'WORDPRESS_...' variables supplied; copying '/usr/src/wordpress/wp-config-docker.php' (WORDPRESS_DB_NAME)

Environment Info

Relevant NPM packages

├─┬ @wordpress/[email protected]
│ ├── [email protected] deduped
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected] deduped
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected] deduped
│ ├── [email protected]
│ ├── [email protected]
│ └── [email protected]

WordPress information

trunk@647a41c

[talldan]

What I don't know is how wp-env previously defined the DB username and password values. (cc @noahtallen, @noisysocks).

Struggling to find a reference to anything like that. Not sure if the docker container is supposed to work without these specified. If so, it may be an upstream issue.

[StevenDufresne]

Also noting that the feature added in the WordPress image was un-betaed yesterday.

docker-library/wordpress@fb920c6

[noisysocks]

What I don't know is how wp-env previously defined the DB username and password values. (cc @noahtallen, @noisysocks).

IIRC these were omitted because the wordpress image defaulted to user = 'root', password = '' which is what the mysql image also defaults to.

[youknowriad]

Tried setting explicitely the environoment variables for user and password to "root" and "" in the docker-compose.yml generated by wp-env and for some reason I didn't manage to make it work

[pierlon]

The wordpress image was previously creating the WordPress database if it did not already exist.

[youknowriad]

Thanks for the hint @pierlon this helped me figure out a potential fix here #29770

[pierlon]

@youknowriad I've also created a PR that reintroduces the feature of creating the database on container startup: docker-library/wordpress#575.

[noahtallen]

Resolved in #29800. This fix will need to be pushed to npm before anyone outside of gutenberg will see it, and I'm not sure when that will happen.

See #29800 (review) for possible follow-up tasks.