Openemr-cmd restore snapshot index corrupted error

Came across a pretty weird error here in making a docker capsule on an external server and trying to restore it on my local machine. I’m wondering if something changed in our openemr-cmd devops. I did a snapshot on a server running against the latest openemr development branch. I have not as yet done any docker image updates yet (both externally / locally). My last updated was about 4 months ago.

Here is the error:
Performing restore from 2023-08-10-rest-api-filter-by-uuid-bugfixes snapshot
Remove database
Remove database user
ERROR 126 (HY000) at line 1: Got error ‘126 “Index is corrupted”’ for ‘./mysql/db.MAI’
Reset couchdb
Remove files
Re-installing OpenEMR
Cannot load Zend OPcache - it was already loaded
PHP Fatal error: Uncaught mysqli_sql_exception: Operation CREATE USER failed for ‘openemr’@’%’ in /var/www/localhost/htdocs/openemr/library/classes/Installer.class.php:1335
Stack trace:
#0 /var/www/localhost/htdocs/openemr/library/classes/Installer.class.php(1335): mysqli_query()
#1 /var/www/localhost/htdocs/openemr/library/classes/Installer.class.php(286): Installer->execute_sql()
#2 /var/www/localhost/htdocs/openemr/library/classes/Installer.class.php(1245): Installer->create_database_user()
#3 /var/www/localhost/htdocs/auto_configure.php(45): Installer->quick_install()
#4 {main}
thrown in /var/www/localhost/htdocs/openemr/library/classes/Installer.class.php on line 1335

I’ll try updating the docker images and see if that resolves the problem, but I wanted to throw that out there in case anyone has seen a similar problem.

So I had to update the docker images using a docker-compose pull and docker-compose restart in order to restore my docker capsule. Apparently there is something in the latest code database changes that don’t play nice with earlier docker images. If others run into this issue, hopefully this solution will help them out.