MySQL in docker can start anymore

[tabvn]

here is an error i got why i try to start mysql in docker. Any solution to fix this. Thank you

 2024-02-13 09:17:54+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.44-1.el7 started.
mysql  | 2024-02-13 09:17:54+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
mysql  | 2024-02-13 09:17:54+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.44-1.el7 started.
mysql  | '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
mysql  | 2024-02-13T09:17:55.014923Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysql  | 2024-02-13T09:17:55.016293Z 0 [Note] mysqld (mysqld 5.7.44) starting as process 1 ...
mysql  | 2024-02-13T09:17:55.019083Z 0 [Note] InnoDB: PUNCH HOLE support available
mysql  | 2024-02-13T09:17:55.019117Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql  | 2024-02-13T09:17:55.019121Z 0 [Note] InnoDB: Uses event mutexes
mysql  | 2024-02-13T09:17:55.019125Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
mysql  | 2024-02-13T09:17:55.019129Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
mysql  | 2024-02-13T09:17:55.019133Z 0 [Note] InnoDB: Using Linux native AIO
mysql  | 2024-02-13T09:17:55.019399Z 0 [Note] InnoDB: Number of pools: 1
mysql  | 2024-02-13T09:17:55.019520Z 0 [Note] InnoDB: Using CPU crc32 instructions
mysql  | 2024-02-13T09:17:55.020916Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
mysql  | 2024-02-13T09:17:55.026584Z 0 [Note] InnoDB: Completed initialization of buffer pool
mysql  | 2024-02-13T09:17:55.028360Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
mysql  | 2024-02-13T09:17:55.039709Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
mysql  | 2024-02-13T09:17:55.040817Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 47779574
mysql  | 2024-02-13T09:17:55.040838Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 47779583
mysql  | 2024-02-13T09:17:55.040843Z 0 [Note] InnoDB: Database was not shutdown normally!
mysql  | 2024-02-13T09:17:55.040848Z 0 [Note] InnoDB: Starting crash recovery.
mysql  | 09:17:55 UTC - mysqld got signal 11 ;
mysql  | This could be because you hit a bug. It is also possible that this binary
mysql  | or one of the libraries it was linked against is corrupt, improperly built,
mysql  | or misconfigured. This error can also be caused by malfunctioning hardware.
mysql  | Attempting to collect some information that could help diagnose the problem.
mysql  | As this is a crash and something is definitely wrong, the information
mysql  | collection process might fail.
mysql  | 
mysql  | key_buffer_size=8388608
mysql  | read_buffer_size=131072
mysql  | max_used_connections=0
mysql  | max_threads=151
mysql  | thread_count=0
mysql  | connection_count=0
mysql  | It is possible that mysqld could use up to 
mysql  | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68199 K  bytes of memory
mysql  | Hope that's ok; if not, decrease some variables in the equation.
mysql  | 
mysql  | Thread pointer: 0x0
mysql  | Attempting backtrace. You can use the following information to find out
mysql  | where mysqld died. If you see no messages after this, something went
mysql  | terribly wrong...
mysql  | stack_bottom = 0 thread_stack 0x40000
mysql  | mysqld(my_print_stacktrace+0x3b)[0xf11c0b]
mysql  | mysqld(handle_fatal_signal+0x486)[0x79f7d6]
mysql  | /lib64/libpthread.so.0(+0xf8c0)[0x7fd2781ce8c0]
mysql  | mysqld(_Z26page_cur_search_with_matchPK11buf_block_tPK12dict_index_tPK8dtuple_t15page_cur_mode_tPmS9_P10page_cur_tP8rtr_info+0x1c1)[0xfda8f1]
mysql  | mysqld(_Z27btr_cur_search_to_nth_levelP12dict_index_tmPK8dtuple_t15page_cur_mode_tmP9btr_cur_tmPKcmP5mtr_t+0x1079)[0x1109f79]
mysql  | mysqld(_Z30btr_pcur_open_on_user_rec_funcP12dict_index_tPK8dtuple_t15page_cur_mode_tmP10btr_pcur_tPKcmP5mtr_t+0x9d)[0x1111eed]
mysql  | mysqld[0x1182c5d]
mysql  | mysqld(_Z19dict_load_sys_tableP12dict_table_t+0x5b)[0x11840fb]
mysql  | mysqld(_Z9dict_bootv+0xe47)[0x1160707]
mysql  | mysqld(_Z34innobase_start_or_create_for_mysqlv+0x42c5)[0x10957d5]
mysql  | mysqld[0xf5a89f]
mysql  | mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x51)[0x7f2671]
mysql  | mysqld[0xcf2c85]
mysql  | mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0xcf8fb0]
mysql  | mysqld[0x797cc4]
mysql  | mysqld(_Z11mysqld_mainiPPc+0xa85)[0x79b4e5]
mysql  | /lib64/libc.so.6(__libc_start_main+0xf5)[0x7fd2764cd555]
mysql  | mysqld[0x78f154]
mysql  | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
mysql  | information that should help you find out what is causing the crash.

[tianon]

mysql  | 2024-02-13T09:17:55.040843Z 0 [Note] InnoDB: Database was not shutdown normally!
mysql  | 2024-02-13T09:17:55.040848Z 0 [Note] InnoDB: Starting crash recovery.
mysql  | 09:17:55 UTC - mysqld got signal 11 ;
mysql  | This could be because you hit a bug. It is also possible that this binary
mysql  | or one of the libraries it was linked against is corrupt, improperly built,
mysql  | or misconfigured. This error can also be caused by malfunctioning hardware.
mysql  | Attempting to collect some information that could help diagnose the problem.
mysql  | As this is a crash and something is definitely wrong, the information
mysql  | collection process might fail.

This sounds like your database got corrupted somehow?

[tabvn]

mysql  | 2024-02-13T09:17:55.040843Z 0 [Note] InnoDB: Database was not shutdown normally!

mysql  | 2024-02-13T09:17:55.040848Z 0 [Note] InnoDB: Starting crash recovery.

mysql  | 09:17:55 UTC - mysqld got signal 11 ;

mysql  | This could be because you hit a bug. It is also possible that this binary

mysql  | or one of the libraries it was linked against is corrupt, improperly built,

mysql  | or misconfigured. This error can also be caused by malfunctioning hardware.

mysql  | Attempting to collect some information that could help diagnose the problem.

mysql  | As this is a crash and something is definitely wrong, the information

mysql  | collection process might fail.

This sounds like your database got corrupted somehow?

Thank you. Yes it's . I can start MySQL with new fresh data . However I can not start MySQL with current data