MARIADB_AUTO_UPGRADE and MARIADB_INITDB_SKIP_TZINFO

[Prinzhorn]

Our Matomo stopped working because MariaDB filled the storage with 35GB of logs of nothing but:

{"log":"2022-07-12 8:00:48 41072 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).\n","stream":"stderr","time":"2022-07-12T08:00:48.123470781Z"} {"log":"2022-07-12 8:00:48 41071 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').\n","stream":"stderr","time":"2022-07-12T08:00:48.125477286Z"}

Seems like we were not the only one affected:

https://mariadb.com/kb/en/the-community-incorrect-definition-of-table-mysqlcolumn_stats-after-upgrade/ https://techoverflow.net/2022/06/07/how-to-fix-docker-mariadb-correct-definition-of-table-mysql-column_stats-expected-column-hist_type-at-position-9/ https://community.home-assistant.io/t/mariadb-errors-after-update/424731 https://bytefreaks.net/applications/docker/incorrect-definition-of-table-mysql-column_stats-expected-column https://github.com/photoprism/photoprism/issues/2382

This should fix it? See also https://github.com/MariaDB/mariadb-docker/issues/350

Originally I did already change image: mariadb to image: mariadb:10 to lock it down a little but somehow I managed to re-use the same volume with a newer MariaDB, I guess (it wouldn't just randomly update the DB for no reason).