all what i know, that succesfully running server rebooted at night and now docker container not working.

`2024-04-25 03:06:41+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
db                    | 2024-04-25 03:06:41+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.36-1.el8 started.
db                    | '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
db                    | 2024-04-25T03:06:42.245413Z 0 [Warning] [MY-011068] [Server] The syntax '--skip-host-cache' is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead.
db                    | 2024-04-25T03:06:42.247519Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.36) starting as process 1
db                    | 2024-04-25T03:06:42.255630Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
db                    | 2024-04-25T03:06:42.355614Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
db                    | 2024-04-25T03:06:42.355653Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3623:err == DB_SUCCESS thread 139719202498304
db                    | InnoDB: We intentionally generate a memory trap.
db                    | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
db                    | InnoDB: If you get repeated assertion failures or crashes, even
db                    | InnoDB: immediately after the mysqld startup, there may be
db                    | InnoDB: corruption in the InnoDB tablespace. Please refer to
db                    | InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
db                    | InnoDB: about forcing recovery.
db                    | 2024-04-25T03:06:42Z UTC - mysqld got signal 6 ;
db                    | Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
db                    | BuildID[sha1]=d0511f6fcf40bda30be3796565c264e503ecc241
db                    | Thread pointer: 0x84bfc50
db                    | Attempting backtrace. You can use the following information to find out
db                    | where mysqld died. If you see no messages after this, something went
db                    | terribly wrong...
db                    | stack_bottom = 7f12e96edba0 thread_stack 0x100000
db                    | /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x2139601]
db                    | /usr/sbin/mysqld(print_fatal_signal(int)+0x2a2) [0xff5f72]
db                    | /usr/sbin/mysqld(my_server_abort()+0x75) [0xff61b5]
db                    | /usr/sbin/mysqld(my_abort()+0xe) [0x213349e]
db                    | /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x309) [0x23846a9]
db                    | /usr/sbin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0x21be) [0x22619be]
db                    | /usr/sbin/mysqld(srv_start(bool)+0x1882) [0x23361a2]
db                    | /usr/sbin/mysqld() [0x2181865]
db                    | /usr/sbin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xca) [0x1edd0aa]
db                    | /usr/sbin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x232) [0x210c132]
db                    | /usr/sbin/mysqld() [0x10ba016]
db                    | /usr/sbin/mysqld() [0x284d0c4]
db                    | /lib64/libpthread.so.0(+0x81da) [0x7f12f7dbd1da]
db                    | /lib64/libc.so.6(clone+0x43) [0x7f12f636be73]
| Trying to get some variables.
db                    | Some pointers may be invalid and cause the dump to abort.
db                    | Query (0): Connection ID (thread ID): 1
db                    | Status: NOT_KILLED`

thanks

docker compose down – ok
docker compose up – db restarting every 5 sek with results above