Fix MySQL CI #612
Merged
Fix MySQL CI #612
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The CI has been failing for a few weeks, it seems since MySQL updated their images: docker-library/mysql@a15b34a.
I don't know exactly what was happening but the MySQL server was not starting and it was complaining about not being able to allocate threads during bootstrap and the data directory being unusable.
After trying many things to get it working with the old image, I found that it just works ™ with this image. The difference is the old image was Alpine 3.13 and this one is Alpine 3.16. Alpine 3.13 was end of life 2 years ago so I guess it makes sense there might be some weird errors when it's used as the host OS for newer images.
With this change we can still keep the Elixir version we were testing against but I couldn't find an acceptable image on
hexpm/elixirwith the Erlang version we were using before. So now we are testing against a slightly newer Erlang.