【Laradock】Mysqlがクラッシュして立ち上がらない

Question

前提・実現したいこと

laradockの環境構築中でdockerにて立ち上げたのですが，Mysqlがクラッシュして立ち上がりません。
立ち上げ方をご教示頂けると幸いです。

発生している問題・エラーメッセージ

laradock_mysql(コンテナでのメッセージ)

2021-04-02 17:06:25+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.33-1debian10 started.
2021-04-02 17:06:25+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2021-04-02 17:06:25+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.33-1debian10 started.
2021-04-02T17:06:26.291050Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2021-04-02T17:06:26.291124Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2021-04-02T17:06:26.291130Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2021-04-02T17:06:26.313957Z 0 [Note] mysqld (mysqld 5.7.33) starting as process 1 ...
2021-04-02T17:06:26.336703Z 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
2021-04-02T17:06:26.342333Z 0 [Note] InnoDB: PUNCH HOLE support available
2021-04-02T17:06:26.342403Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-04-02T17:06:26.342412Z 0 [Note] InnoDB: Uses event mutexes
2021-04-02T17:06:26.342418Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2021-04-02T17:06:26.342423Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-04-02T17:06:26.342430Z 0 [Note] InnoDB: Using Linux native AIO
2021-04-02T17:06:26.342810Z 0 [Note] InnoDB: Number of pools: 1
2021-04-02T17:06:26.342993Z 0 [Note] InnoDB: Using CPU crc32 instructions
2021-04-02T17:06:26.347234Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-04-02T17:06:26.374862Z 0 [Note] InnoDB: Completed initialization of buffer pool
2021-04-02T17:06:26.378866Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-04-02T17:06:26.482105Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
2021-04-02 17:06:26 0x7fac7d8b9740 InnoDB: Assertion failure in thread 140378817402688 in file ut0ut.cc line 921

InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
17:06:26 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=
max_threads=151
thread_count=
connection_count=0
It is possible that mysqld could use up t
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68196 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
mysqld(my_print_stacktrace+0x2c)[0x560d3677e6bc]
mysqld(handle_fatal_signal+0x501)[0x560d360950c1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7fac7de1a730]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7fac7d8f57bb]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7fac7d8e0535]

mysqld(+0x6c40bf)[0x560d3605c0bf]
mysqld(+0x6c449d)[0x560d3605c49d]
mysqld(+0x11b303c)[0x560d36b4b03c]
mysqld(+0x11b366e)[0x560d36b4b66e]
mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x312)[0x560d36b52f12]
mysqld(+0x11732db)[0x560d36b0b2db]
mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0x37)[0x560d36b0bb27]
mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x409)[0x560d36ae0bd9]
mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x13e)[0x560d36a7de9e]
mysqld(+0x10b7b47)[0x560d36a4fb47]
mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f67)[0x560d36a53707]
mysqld(+0xf8c9e0)[0x560d369249e0]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x55)[0x560d360e62f5]
mysqld(+0xbe3346)[0x560d3657b346]
mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x1dc)[0x560d3657d21c]
mysqld(+0x6f603e)[0x560d3608e03e]
mysqld(_Z11mysqld_mainiPPc+0x758)[0x560d3608f4e8]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7fac7d8e209b]
mysqld(_start+0x2a)[0x560d36085d9a]

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

該当のソースコード

※変更箇所のみ抜粋
変更箇所はMYSQL_VERSIOの部分のみ

docker-compose.yml

### MySQL ################################################
    mysql:
      build:
        context: ./mysql
        args:
          - MYSQL_VERSION=5.7
      environment:
        - MYSQL_DATABASE=${MYSQL_DATABASE}
        - MYSQL_USER=${MYSQL_USER}
        - MYSQL_PASSWORD=${MYSQL_PASSWORD}
        - MYSQL_ROOT_PASSWORD=${MYSQL_ROOT_PASSWORD}
        - TZ=${WORKSPACE_TIMEZONE}
      volumes:
        - ${DATA_PATH_HOST}/mysql:/var/lib/mysql
        - ${MYSQL_ENTRYPOINT_INITDB}:/docker-entrypoint-initdb.d
      ports:
        - "${MYSQL_PORT}:3306"
      networks:
        - backend   

.env

### MYSQL #################################################

MYSQL_VERSION=5.7
MYSQL_DATABASE=default
MYSQL_USER=default
MYSQL_PASSWORD=secret
MYSQL_PORT=3306
MYSQL_ROOT_PASSWORD=root
MYSQL_ENTRYPOINT_INITDB=./mysql/docker-entrypoint-initdb.d

env-example

### MYSQL #################################################

MYSQL_VERSION=5.7
MYSQL_DATABASE=default
MYSQL_USER=default
MYSQL_PASSWORD=secret
MYSQL_PORT=3306
MYSQL_ROOT_PASSWORD=root
MYSQL_ENTRYPOINT_INITDB=./mysql/docker-entrypoint-initdb.d

試したこと

・コンテナの削除
・イメージの削除
・ボリュームの削除
・再起動

補足情報（FW/ツールのバージョンなど）

windows10 Pro
docker desktop

Answer 1

既にmysqlのデータが存在しており、何らかの不整合が発生してエラーになっていたようです。

「./ibdata1というファイル内のflagに誤りがある」というエラーから
自身の環境の~/.laradock以下を確認するとibdata1というファイルがあったので、恐らく古いファイルが残っているのだろうと推測できた、という流れ。

エラー内容

2021-04-02T17:06:26.482105Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!

コンテナを停止する

docker-compose down

mysqlのボリュームを削除する

docker volume rm laradock_mysql

mysqlのデータを削除する

rm -r -fo  ~/.laradock/data/mysql

※Macの場合　
rm -rf ~/.laradock/data/mysql

コンテナを起動する

docker-compose up -d php-fpm nginx mysql phpmyadmin workspace

上記順番にコマンドを打ったら解決できました。