When a new version of MariaDB is available, and a rebuild is used; the database no longer be allowed to boot.
From my understanding this is due to that on rebuild, the database is killed instead of gracefully shut down.
Currently you have to manually roll back the version in your .lando.local.yml, rebuild, stop, remove the .lando.local.yml version constraint and rebuild again to allow the DB to update.
Example error:
InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.4.17.
After mariadb was updated to 10.11
Related: #36
When a new version of MariaDB is available, and a rebuild is used; the database no longer be allowed to boot.
From my understanding this is due to that on rebuild, the database is killed instead of gracefully shut down.
Currently you have to manually roll back the version in your .lando.local.yml, rebuild, stop, remove the .lando.local.yml version constraint and rebuild again to allow the DB to update.
Example error:
After mariadb was updated to 10.11
Related: #36