Closed seikettune closed 6 months ago
Sounds like you're getting bitten by the recent update to the new 8.4 upstream release. I would suggest pinning to a more specific version of MySQL (and checking the MySQL 8.4 release notes for clues to why your updated deployment is failing).
@tianon yup that was indeed the case.
I updated the mysqld command to match the latest mysql specs.
How it was: command: mysqld --default_authentication_plugin=mysql_native_password --character-set-server=utf8mb4 --collation-server=utf8mb4_swedish_ci
How it is now: command: mysqld --mysql-native-password=ON --authentication_policy=mysql_native_password --character-set-server=utf8mb4 --collation-server=utf8mb4_swedish_ci
Mysql-native-password=ON to meet the needs of wordpress.
With the caveat/warning that they do intend to remove that functionality completely in the future (so eventually the square wheel will roll again and this will come back out from under the rug :see_no_evil:).
I'm using using mysql image with tag :latest. While building I get following errors (among many others but I assume that container fails to run correctly due either one or both of these errors?
What gives? I'm totally lost here and I've tried everything I can imagine that could cause this.
Also note that my mysql container was functioning just fine a while ago.
Here's my docker-compose.yml: