chore: switch from bitnami/mariadb to standard mariadb:10.11#5
Conversation
The bitnami/mariadb image offers no advantages over the official mariadb image for this use case. Switch to the official image and: - Pin to 10.11 LTS (bitnami/mariadb:latest resolves to 12.x which triggers InnoDB error 1020 in the Harvester stager) - Use the standard data directory /var/lib/mysql instead of the bitnami-specific /bitnami/mariadb MARIADB_* env var names are unchanged; the official mariadb image has supported them since 10.4. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
This PR updates the local/CI Docker Compose stack to use the official MariaDB image pinned to the 10.11 LTS line to avoid issues seen with the Bitnami latest tag drifting to 12.x.
Changes:
- Switch MariaDB service image from
bitnami/mariadb:latesttomariadb:10.11. - Update the MariaDB data volume mount path from
/bitnami/mariadbto/var/lib/mysql.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| volumes: | ||
| - harvester-db-data:/bitnami/mariadb | ||
| - harvester-db-data:/var/lib/mysql |
There was a problem hiding this comment.
Changing the mount point for the existing named volume harvester-db-data from /bitnami/mariadb to /var/lib/mysql will make any previously-initialized data in that volume invisible to the new container (effectively starting with an empty datadir), which can look like accidental data loss and can break local dev/CI runs that reuse volumes. Consider either renaming the volume (so the new image gets a fresh volume) or adding an explicit migration/reset note next to this volume line (e.g., requiring docker compose down -v when switching images).
What
Replace
bitnami/mariadb:latestwithmariadb:10.11(official Docker Hub image).Why
bitnami/mariadb:latestcurrently resolves to 12.x, which triggers InnoDB error 1020 ("Record has changed since last read") in the Harvester stager'sSELECT ... FOR UPDATE/UPDATEpattern — causing jobs to stall into_transferstateChanges
image: bitnami/mariadb:latestimage: mariadb:10.11/bitnami/mariadb/var/lib/mysqlMARIADB_*env var names are unchanged — the official image supports them since 10.4.