-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
latest image has no connection #1048
Comments
I'm having the same issue following upgrade to mysql:8.4.0, however rolling back to mysql:8.3.0 doesn't work (only permitted between patch releases.) Container logs: 2024-05-01T15:18:35.265911Z 0 [System] [MY-015015] [Server] MySQL Server - start. Any assistance will be appreciated as I'm at a dead end. |
mysql:8.4.0 gives this message with
|
Yes, the same here. A real disaster... You are not alone. ;) |
Sort of related to #1039 |
Awesome - thanks! |
|
I would recommend reading at least the full https://dev.mysql.com/blog-archive/introducing-mysql-innovation-and-long-term-support-lts-versions/ would also be good to read about when updates or breaking changes happen. TL;DR: add I'd also recommend moving away from |
@yosifkit Thanks for clarification. |
Yep, the same here with Ghost (CMS), what nightmare. |
A little correction here. I was facing the same issue on the TLDR: Remove the |
I believe the upstream intent is to completely remove the functionality, so don't be surprised when you find that can again after kicking it down the road (again). 😅 |
fyi the the documentation at https://hub.docker.com/_/mysql currently has an example showing
|
Good callout, thank you! docker-library/docs#2443
|
I have an CI/CD that is configured to run integration tests and it uses mysql docker image for it. Previously it run without problem, but today all tests are failed cause cannot connect to database.
For database startup I have follow configuration. As you can see it is not specified with image tag so it uses
latest
.After investigation I found out that success builds uses
mysql:8.3.0
(sha256:9de9d54fecee6253130e65154b930978b1fcc336bcc86dfd06e89b72a2588ebe) and failed usesmysql:8.4.0
(sha256:f7a8e140a7d6d1e6e0c99eeb0489c50a186ee4ac44ff55323a176529b9a43d33).I changes my
test-db.yml
to use imagemysql:8.3.0
and it works.The service is started without error. There are logs from CI/CD:
And corresponding messages in tests:
The text was updated successfully, but these errors were encountered: