Cannot open datafile for read-only: 'mysql.ibd' OS error: 71 (docker compose upgrade)

[baroo_zabbix]

Hi. I`m trying to upgrade my docker compose installation of zabbix from version 4.0.4 to 7.2 (mysql form 5.7 to 8.4) and during the startup of mysql container I get the following log:

2025-02-01 06:30:29+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.4-1.el9 started.
2025-02-01 06:30:31+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2025-02-01 06:30:31+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.4-1.el9 started.
'/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
2025-02-01T06:30:31.731664Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2025-02-01T06:30:31.918223Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.4) starting as process 1
2025-02-01T06:30:31.991898Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-02-01T06:30:34.920488Z 1 [ERROR] [MY-012592] [InnoDB] Operating system error number 2 in a file operation.
2025-02-01T06:30:34.920554Z 1 [ERROR] [MY-012593] [InnoDB] The error means the system cannot find the path specified.
2025-02-01T06:30:34.920571Z 1 [ERROR] [MY-012216] [InnoDB] [COLOR=#e74c3c]Cannot open datafile for read-only: 'mysql.ibd' OS error: 71
mysqld: Can't open file: 'mysql.ibd' (errno: 0 - )[/COLOR]
2025-02-01T06:30:35.408233Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2025-02-01T06:30:35.408431Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2025-02-01T06:30:35.408479Z 0 [ERROR] [MY-010119] [Server] Aborting
2025-02-01T06:30:35.409390Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.4.4)  MySQL Community Server - GPL.
2025-02-01T06:30:35.409462Z 0 [System] [MY-015016] [Server] MySQL Server - end.

I`m fairly sure that data directory for mysql is set properly as mysql is creating new some new files during startup process:

-rw-r----- 1 999 docker 56 Jan 30 2019 auto.cnf
-rw-r----- 1 999 systemd-journal 0 Feb 1 07:30 binlog.index
-rw------- 1 999 docker 1679 Jan 30 2019 ca-key.pem
-rw-r--r-- 1 999 docker 1107 Jan 30 2019 ca.pem
-rw-r--r-- 1 999 docker 1107 Jan 30 2019 client-cert.pem
-rw------- 1 999 docker 1675 Jan 30 2019 client-key.pem
-rw-r----- 1 999 systemd-journal 6291456 Feb 1 11:18 '#ib_16384_0.dblwr'
-rw-r----- 1 999 systemd-journal 14680064 Feb 1 07:30 '#ib_16384_1.dblwr'
-rw-r----- 1 999 systemd-journal 15566 Feb 1 06:37 ib_buffer_pool
-rw-r----- 1 999 docker 79691776 Feb 1 11:18 ibdata1
drwxr-x--- 2 999 systemd-journal 4096 Feb 1 11:18 '#innodb_redo'
drwxr-x--- 2 999 systemd-journal 4096 Feb 1 11:18 '#innodb_temp'
drwxr-x--- 2 999 docker 4096 Jan 30 2019 mysql
lrwxrwxrwx 1 999 systemd-journal 27 Feb 1 11:18 mysql.sock -> /var/run/mysqld/mysqld.sock
drwxr-x--- 2 999 docker 4096 Jan 30 2019 performance_schema
-rw------- 1 999 docker 1675 Jan 30 2019 private_key.pem
-rw-r--r-- 1 999 docker 451 Jan 30 2019 public_key.pem
-rw-r--r-- 1 999 docker 1107 Jan 30 2019 server-cert.pem
-rw------- 1 999 docker 1679 Jan 30 2019 server-key.pem
drwxr-x--- 2 999 docker 12288 Jan 30 2019 sys
-rw-r----- 1 999 systemd-journal 16777216 Feb 1 07:30 undo_001
-rw-r----- 1 999 systemd-journal 16777216 Feb 1 07:30 undo_002
drwxr-x--- 2 999 docker 16384 Jan 30 2019 zabbix

but there is in fact no "mysql.ibd" file. How should I propoery upgrade that database in this case?