Failing on mac M1

[juancresc]

This is the compose file I'm using

  db:
    restart: "no"
    image: biarms/mysql:5.7
    ports:
      - '3306:3306'
    environment:
      MYSQL_DATABASE: demo
      MYSQL_USER: user
      MYSQL_PASSWORD: test
      MYSQL_ROOT_PASSWORD: test
    volumes:
      - './dump:/docker-entrypoint-initdb.d'
      - 'persistent:/var/lib/mysql'
    networks:
      - default

And this is the error

db_1          | 2022-11-25T18:40:27.530844Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
db_1          | 2022-11-25T18:40:27.591940Z 0 [Note] InnoDB: Completed initialization of buffer pool
db_1          | 2022-11-25T18:40:27.618343Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
db_1          | 2022-11-25T18:40:27.641747Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
db_1          | 2022-11-25 19:40:27 0x400338cd40  InnoDB: Assertion failure in thread 274931961152 in file ut0ut.cc line 918
db_1          | InnoDB: We intentionally generate a memory trap.
db_1          | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
db_1          | InnoDB: If you get repeated assertion failures or crashes, even
db_1          | InnoDB: immediately after the mysqld startup, there may be
db_1          | InnoDB: corruption in the InnoDB tablespace. Please refer to
db_1          | InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
db_1          | InnoDB: about forcing recovery.
db_1          | 18:40:27 UTC - mysqld got signal 6 ;
db_1          | This could be because you hit a bug. It is also possible that this binary
db_1          | or one of the libraries it was linked against is corrupt, improperly built,
db_1          | or misconfigured. This error can also be caused by malfunctioning hardware.
db_1          | Attempting to collect some information that could help diagnose the problem.
db_1          | As this is a crash and something is definitely wrong, the information
db_1          | collection process might fail.
db_1          | 
db_1          | key_buffer_size=16777216
db_1          | read_buffer_size=262144
db_1          | max_used_connections=0
db_1          | max_threads=151
db_1          | thread_count=0
db_1          | connection_count=0
db_1          | It is possible that mysqld could use up to 
db_1          | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 66724 K  bytes of memory
db_1          | Hope that's ok; if not, decrease some variables in the equation.
db_1          | 
db_1          | Thread pointer: 0x0
db_1          | Attempting backtrace. You can use the following information to find out
db_1          | where mysqld died. If you see no messages after this, something went
db_1          | terribly wrong...
db_1          | stack_bottom = 0 thread_stack 0x30000
db_1          | /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xeb5b7b]
db_1          | /usr/sbin/mysqld(handle_fatal_signal+0x377)[0x779037]
db_1          | /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x4002232890]
db_1          | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x4002dbee97]
db_1          | /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x4002dc0801]
db_1          | /usr/sbin/mysqld[0x74f5d4]
db_1          | /usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0x66)[0x108d1a6]
db_1          | /usr/sbin/mysqld[0x113950b]
db_1          | /usr/sbin/mysqld[0x1139a9d]
db_1          | /usr/sbin/mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x322)[0x1145b82]
db_1          | /usr/sbin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xdd)[0x10f8bdd]
db_1          | /usr/sbin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4e5)[0x10ca805]
db_1          | /usr/sbin/mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x14f)[0x106b71f]
db_1          | /usr/sbin/mysqld[0x1032a78]
db_1          | /usr/sbin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2e3d)[0x1036dfd]
db_1          | /usr/sbin/mysqld[0xefd31d]
db_1          | /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x7ccf3f]
db_1          | /usr/sbin/mysqld[0xc8b695]
db_1          | /usr/sbin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x1e5)[0xc8ebb5]
db_1          | /usr/sbin/mysqld[0x771410]
db_1          | /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x795)[0x772b15]
db_1          | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x4002da1b97]
db_1          | /usr/sbin/mysqld(_start+0x2a)[0x768e6a]
db_1          | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
db_1          | information that should help you find out what is causing the crash.

[juancresc]

this was due to an old volume