Running MariaDB in Docker with prorm

Running MariaDB in Docker with prorm MariaDB is wire-compatible with MySQL but diverges enough that prorm ships a separate mariadb dialect — notably for system-versioned (temporal) tables, RETURNING support, and sequence handling. Start the container Note the host port is 3307, so MariaDB and MySQL can run side by side — that is how the repository's compose file is set up. Waiting for readiness The MariaDB image ships a purpose-built script: Connect prorm to it A worked example System-versioned tables MariaDB can keep the full history of a row and query it as of a point in time — something MySQL has no equivalent for. prorm exposes it through the MariaDB dialect; see the dialect page for the WITH SYSTEM VERSIONING options and FOR SYSTEMTIME AS OF queries. Tear down Troubleshooting Symptom | Cause | --- | --- | Connecting to 3306 hits MySQL | MariaDB publishes 3307 on the host in this setup. | healthcheck.sh: not found | Older images lack it — fall back to mysqladmin ping -uroot -prootpass. | Temporal DDL rejected | System versioning needs MariaDB 10.3+; the mariadb:11 image is fine, an older one may not be. | Access denied after changing env | The env vars only seed a fresh data directory; remove the volume. | Related reading MariaDB dialect MySQL in Docker — the sibling setup