Docker Easy startup problems

I’ve got the latest code and just run docker-compose up.

Most every thing looks to be fine except when it gets to Mariadb, docker shows it in a constant loop of “restarting” and I’m getting these messages in my vs code terminal:

development-easy-mysql-1 | 2023-08-21 15:36:38+00:00 [Note] [Entrypoint]: Switching to dedicated user ‘mysql’
development-easy-mysql-1 | 2023-08-21 15:36:38+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.5+maria~ubu2204 started.
development-easy-mysql-1 | 2023-08-21 15:36:38+00:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
development-easy-mysql-1 | 2023-08-21 15:36:38 0 [Note] Starting MariaDB 10.11.5-MariaDB-1:10.11.5+maria~ubu2204 source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 1
development-easy-mysql-1 | 2023-08-21 15:36:38 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
development-easy-mysql-1 | 2023-08-21 15:36:38 0 [Note] InnoDB: Using transactional memory
development-easy-mysql-1 | 2023-08-21 15:36:38 0 [Note] InnoDB: Number of transaction pools: 1
development-easy-mysql-1 | 2023-08-21 15:36:38 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
development-easy-mysql-1 | 2023-08-21 15:36:38 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
development-easy-mysql-1 | 2023-08-21 15:36:38 0 [Note] InnoDB: Using liburing
development-easy-mysql-1 | 2023-08-21 15:36:38 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
development-easy-mysql-1 | 2023-08-21 15:36:38 0 [Note] InnoDB: Completed initialization of buffer pool
development-easy-mysql-1 | 2023-08-21 15:36:38 0 [Note] InnoDB: File system buffers for log disabled (block size=4096 bytes)
development-easy-mysql-1 | 2023-08-21 15:36:38 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.6.12. You must start up and shut down MariaDB 10.7 or earlier.
development-easy-mysql-1 | 2023-08-21 15:36:38 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
development-easy-mysql-1 | 2023-08-21 15:36:38 0 [Note] InnoDB: Starting shutdown…
development-easy-mysql-1 | 2023-08-21 15:36:39 0 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
development-easy-mysql-1 | 2023-08-21 15:36:39 0 [Note] Plugin ‘FEEDBACK’ is disabled.
development-easy-mysql-1 | 2023-08-21 15:36:39 0 [ERROR] Unknown/unsupported storage engine: InnoDB
development-easy-mysql-1 | 2023-08-21 15:36:39 0 [ERROR] Aborting
development-easy-mysql-1 exited with code 1

False alarm. I considered deleting this thread, but maybe I can note something to help somebody.

After updating my fork, in docker I deleted my images and containers. I thought that was all that was needed. I didn’t notice, or really look for the “volumes” tab in dockers. I saw it after I started this thread. Anyway, once I noticed it I deleted every volume too. That fixed the problem.

I had noticed the build was going a lot faster than I though it should, that should have given me a clue that something was still in memory.

Anyway, I hope this helps someone later down the line.

I ran into a similar problem. The latest docker images need to have the mysql volume restarted as the data folders are not compatible unless you do a mysql_upgrade in the table. Best option is to snapshot the data, pull out the snapshot destroy everything and then you can restore the snapshot.

1 Like