chore(docker): bump PostgreSQL to 18.1 and MySQL to 8.4.10#9003
Open
DoDiODev wants to merge 1 commit into
Open
chore(docker): bump PostgreSQL to 18.1 and MySQL to 8.4.10#9003DoDiODev wants to merge 1 commit into
DoDiODev wants to merge 1 commit into
Conversation
Bump database engine images across the dev, devcontainer, temporal deployment and remote e2e compose files: PostgreSQL 17.2/14.2 to 18.1 and MySQL 8/8.0.26 to 8.4.10. For PostgreSQL 18 the remote e2e volume is mounted at /var/lib/postgresql (parent of the new versioned data dir) instead of /var/lib/postgresql/data, and the Grafana datasource provisioning sets postgresVersion to 1800. Grafana database env parametrization is intentionally out of scope. Signed-off-by: DoDiODev <DoDiDev@proton.me>
This file contains hidden or 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
1 participant
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.
Summary
Bump the database engine images used by the local dev, devcontainer, temporal deployment and remote e2e compose files:
17.2(dev) /14.2-alpine(e2e) ->18.1/18.1-alpine8/8.0.26->8.4.10Details
backend/test/e2e/remote/docker-compose.test.ymlnow mounts thepostgres-testvolume at/var/lib/postgresql(the parent of PostgreSQL 18's new versioned data directory) instead of the legacy/var/lib/postgresql/data, matching the layout already used bydocker-compose-dev-postgresql.yml.grafana/scripts/entrypoint.shsetspostgresVersionto1800so the provisioned PostgreSQL datasource targets PostgreSQL 18.Related / dependencies
fix(dalgorm): make DropIndexes idempotent by skipping missing indexes). It is a functionally independent fix, but without it a pre-existing migration (change _tool_sonarqube_issue_code_blocks.component type to text) aborts on PostgreSQL withSQLSTATE 42704when dropping an already-absent index. That failure is unrelated to the image bumps here, but it does surface during the PostgreSQL migration run. On MySQL this PR is unaffected by fix(dalgorm): make DropIndexes idempotent by skipping missing indexes #9001.Out of scope
Testing
docker compose config -qpasses for all changed compose files.bash -n grafana/scripts/entrypoint.shpasses.FORCE_MIGRATION=true, container starts and accepts connections, migrations complete (with fix(dalgorm): make DropIndexes idempotent by skipping missing indexes #9001 applied),/readyOK, Grafana datasource targets PG18; volume persists across restart.Rollback
Revert this commit to restore the previous image tags and the legacy e2e volume mount.