mariadb:latest Docker image tag produces non-deterministic deployments and silent breaking upgrades #12
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The database service in
docker-compose.ymlusesimage: mariadb:latest, which resolves to a different image each time thelatesttag is updated by the MariaDB project.Location
docker-compose.yml, line 4Risk
A future MariaDB major release published under
latestcan silently introduce breaking changes in SQL syntax, authentication plugins, or default settings (e.g., MariaDB 11.x changed several defaults around character sets and strict mode). This can break the application or migrations on the nextdocker compose buildwith no code change and no easy rollback path, since the previous image layer is no longer tagged.Suggested fix direction
Pin to a specific minor version (e.g.,
mariadb:10.11) and upgrade deliberately through tested version bumps.Severity
minor
Found by
Automated audit by Claude Code