Bump mariadb version to fix dev and e2e docker setup #3665
+8
−8
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
annemirasol
force-pushed
the
dev/gh-worfklow-container
branch
from
1341f43 to
291a8a1
Compare
annemirasol
force-pushed
the
dev/gh-worfklow-container
branch
from
5beacc5 to
82573e4
Compare
annemirasol
changed the title
annemirasol
force-pushed
the
dev/gh-worfklow-container
branch
from
888bfa7 to
507dac5
Compare
annemirasol
requested review from
a team and
Mayisha
and removed request for
a team
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.
Changes proposed in this Pull Request:
Our Github workflow e2e runs have been failing, stuck at
Waiting for containers.... For example, this run.When performing a fresh local dev docker setup, it also gets stuck with
Waiting until the service is ready....This is due to a
mariadberror:mysqlcheck: Got error: 2026: TLS/SSL error: SSL is required, but the server does not support it when trying to connect. Using an updatedmariadbfixes this.This PR also updates an instance of
docker-compose(v1) todocker compose(v2), as the latest Ubuntu is already on v2.Testing instructions
Waiting for containers....npm run downdocker system prune -a -fnpm run upchangelog.txtandreadme.txt(or does not apply)Post merge