There is an upstream issue for the MySQL Docker image that’s affecting users using the v5.7 release (i.e. circleci/mysql:5.7). More specifically, it’s pulling in a broken MySQL v5.7.28 image. You can find the Issue thread here.
Temporary Solution
Instead of using:
circleci/mysql:5.7
use:
circleci/mysql:5.7.27
This will give you the second to last point release, MySQL v5.7.27, which is working in our images as well as upstream.
I’ll update this post again sometime in the future when upstream resolves the issue with the 5.7.28 release.
Upstream has fixed the issue. They should have new images within the hour which means we (CircleCI) will hopefully have new, fixed, images within 2 hours.
Thank you for the update on this. We are using the mysql image directly (mysql:5.7) and it is still not working. Is there something that gets cached that would prevent the build from pulling in the newest build on the 5.7 tag?
The latest output from a build a couple minutes ago shows the following:
Starting container mysql:5.7
using image mysql@sha256:84e9114d9511d380c255fbaec68ede96921c48108d6560edafa302c0e394c47f