(This is the change we comitted to make in #557 that needs to be merged before we send 24c4469 downstream. 👍)

Just to make sure the important bits / migration path for users are in more places they might look when things don't seem to be working the same way they used to, see #557 (comment):

For users who are changing WORDPRESS_* variables and expecting our docker-entrypoint.sh to update them, the "migration" path is to remove your wp-config.php file and let the new entrypoint copy in the updated version, and everything will "just work" from then on.

Noting that this PR broken @wordpress/env or wp-env. We're still trying to understand it exactly here WordPress/gutenberg#29752

@tianon This PR removes the code to create the database in the entrypoint, is that intended behaviour going forward ?. if so we should update the docs at https://hub.docker.com/_/wordpress?tab=tags

Yep, that was intentional -- see docker-library/docs#1892, especially docker-library/docs#1892 (comment):

Creating the database should not have been the job of the WordPress container since that means the database user has more access than it needs to store WordPress data.

Both the mysql and mariadb images have support for creating a database and user with limited access (as is done in the example WordPress stack.yml here)