mysql docker Падение - контейнер останавливается, завершается

Для конфига:

  mysql_old:
    image: mysql:latest
    # command: --mysql-native-password=ON
    container_name: test_mysql_container_termination_db_mysql
    volumes:
      - '../input:/var/www/input'
      - './config/mysql:/docker-entrypoint-initdb.d'
    environment:
      MYSQL_ROOT_PASSWORD: ktu-migrate_root
      MYSQL_USER: ktu-migrate_user
      MYSQL_PASSWORD: ktu-migrate_password
      MYSQL_MULTIPLE_DATABASES: ktu-migrate_mysql_db
    ports:
      - 21211:3306

При запуске без d получаем:

[ERROR] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-001146 - Table 'mysql.component' doesn't exist
test_mysql_container_termination_db_mysql | 2025-05-17T15:25:24.341988Z 0 [Warning] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-003543 - The mysql.component table is missing or has an incorrect definition.
test_mysql_container_termination_db_mysql | 2025-05-17T15:25:24.343270Z 0 [ERROR] [MY-010326] [Server] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
test_mysql_container_termination_db_mysql | 2025-05-17T15:25:24.343318Z 0 [ERROR] [MY-010952] [Server] The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.
test_mysql_container_termination_db_mysql | 2025-05-17T15:25:24.343434Z 0 [ERROR] [MY-010119] [Server] Aborting
test_mysql_container_termination_db_mysql | 2025-05-17T15:25:25.894983Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 9.3.0) MySQL Community Server - GPL.
test_mysql_container_termination_db_mysql | 2025-05-17T15:25:25.894997Z 0 [System] [MY-015016] [Server] MySQL Server - end.

Как решали

Решили удалением контейнера по его имени, почему-то он был ранее создан "неправильно"