Step 1: Find the name of your wp-env container
First, you need to locate the name of the container created by wp-env. To do this, in the directory of your project containing .wp-env.json, you must run the following command:
This should give you a list of containers. In the Names column, you’ll see the following information:
7b3099bc856ae9db898a196c0465cadb_wordpress_1 7b3099bc856ae9db898a196c0465cadb_tests-wordpress_1 7b3099bc856ae9db898a196c0465cadb_mysql_1
In this example, “7b3099bc856ae9db898a196c0465cadb” is the name of the container created by wp-env.
Step 2: Access the directory containing your docker-compose file
Once you have the name of your wp-env container, you can use it to access the directory containing the docker-compose file created by wp-env. To do so, run the following command in your terminal:
cd ~/.wp-env/7b3099bc856ae9db898a196c0465cadb docker-compose down -v docker-compose up -d
This should create a fresh environment.
Step 3: Restart wp-env
Finally, go back to your project folder and run:
You should then receive a message informing you that your WordPress dev environment is ready.
Source: How to Fix MariaDB Error 1130 with wp-env and Docker https://greys.co/how-to-fix-mariadb-error-1130-wp-env-docker/