Skip to content
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

@wordpress/env: Getting error on version 9.3.0 when run start command #59232

Closed
ravinderk opened this issue Feb 21, 2024 · 10 comments · Fixed by #59237
Closed

@wordpress/env: Getting error on version 9.3.0 when run start command #59232

ravinderk opened this issue Feb 21, 2024 · 10 comments · Fixed by #59237
Labels
[Tool] Env /packages/env [Type] Bug An existing feature does not function as intended

Comments

@ravinderk
Copy link

ravinderk commented Feb 21, 2024

Description

I am getting the following error when running wp-env start:

image
@ravinderk ravinderk added the [Type] Bug An existing feature does not function as intended label Feb 21, 2024
@ravinderk ravinderk changed the title Getting error on @wordpress/env@9.3.0 when run start command @wordpress/env: Getting error on version 9.3.0 when run start command Feb 21, 2024
@dmaziar
Copy link

dmaziar commented Feb 21, 2024

The same problem on lower version (8.11.0). Any workaround for this problem?

@adimoldovan
Copy link

Probably caused by MariaDB/mariadb-docker#560?

@ramonschriks
Copy link

ramonschriks commented Feb 21, 2024

The same problem on lower version (8.11.0). Any workaround for this problem?

If you want quick workaround to make it work again for now, you could edit the file below:

node_modules/@wordpress/env/lib/build-docker-compose-config.js

to update the mysql and tests-mysql image from mariadb to mariadb:11.2.2-jammy
(or run: sed -i -e "s/image: 'mariadb'/image: 'mariadb:11.2.2-jammy'/g" node_modules/@wordpress/env/lib/build-docker-compose-config.js)

Run wp-env stop and start again will make it work again.

@sweber83
Copy link

sweber83 commented Feb 21, 2024

I think the root of the issue here is that @wordpress/env implicitly uses the mariadb:latest tag, which is a development release.
So @wordpress/env should instead use a stable release, e.g. mariadb:10.2.

https://mariadb.com/kb/en/mariadb-server-release-dates/
https://hub.docker.com/_/mariadb

Edit:
I meant 11.2 not 10.2

@swissspidy
Copy link
Member

swissspidy commented Feb 21, 2024

:latest is the latest stable release, which at the moment is 11.3.2 (released yesterday). 11.4.x is the development version at the moment.

Choosing something like v10.2 doesn't make sense because that version is 7 years old and hasn't been supported for over 2 years. If anything, choose mariadb:lts to get the LTS version.

@sweber83
Copy link

sweber83 commented Feb 21, 2024

@swissspidy
11.3.x is also a dev release, just like 11.4.x.
See https://mariadb.com/kb/en/mariadb-server-release-dates/

@swissspidy
Copy link
Member

IDK, their download page says it's the latest GA release, and 11.4 is marked as development.

Screenshot 2024-02-21 at 14 25 45

@sweber83
Copy link

The fact that :latest points to 11.3 also indicates it's a stable release 🤷‍♂️

@ravinderk
Copy link
Author

@t-hamano When can we expect a release with this?

@t-hamano
Copy link
Contributor

I'm not sure about the exact release date, but it looks like the RC version is already ready, so I believe it will be released soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Tool] Env /packages/env [Type] Bug An existing feature does not function as intended
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants