Comments - Database Fails To Start After Docker Upgrade
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
I have remembered - I did rename the ib_logfile0 to a .old - someone suggested this in another forum.
Should I put it back and grab a new excerpt from the log?
A docker inspect 51ca0cc3bcac should have ENV MARIADB_VERSION=... which shows the old version.
Yes, move ib_logfile0 back and don't touch it. The existence of these forms of bad advices on multiple forums as resulted in many corrupt database.
Its likely that the upgrade wants a clean shutdown in which case start up the previous version and shut it down cleanly. Ensure compose doesn't get impatient and kill it off during the shutdown.
After the clean shutdown is performed, try the new version again.
Slow running containers is likely to be a different problem. Increased --innodb-buffer-pool-size=512M as an argument or kernel related (I can tell your on an old kernel due to ENOSYS for uring).