Docker v4.42.1 update BROKE MySQL, now looping

1

I traced the issued to a corrupted InnoDB undo log file, undo_001, in the MySQL data directory (C:\opt\xibo\shared\db). This corruption is preventing MySQL from starting. Unfortunately, I don’t know how to repair it. Any ideas? Can I delete xibo-cms-db-1 and reinstall?

2

If you have a recent backup, try restoring it as this may be the fastest option.

If no backup exists, add this line to your my.cnf or my.ini under the [mysqld] section:
innodb_force_recovery = 1
Then restart xibo-cms-db-1.

  • If it starts: Immediately create a backup using e.g. mysqldump
  • If it fails: Try gradually increasing the value (up to 6) until the DB starts.

Another approch could be to first revert to your previous Xibo/Docker version, perform a slow shutdown (by setting innodb_fast_shutdown=0)
then upgrade again.