Как решить проблему с mysql 5.7 «TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option»?

Question

[Руслан Абсалямов]

У меня проблема в том что я запустил весь проект, только mysql у меня выдает ошибки

mysql_kfnp_yii2 | 2019-10-06T18:18:52.515584Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysql_kfnp_yii2 | 2019-10-06T18:18:52.524840Z 0 [Note] mysqld (mysqld 5.7.27) starting as process 1 ...
mysql_kfnp_yii2 | 2019-10-06T18:18:52.541134Z 0 [Note] InnoDB: PUNCH HOLE support available
mysql_kfnp_yii2 | 2019-10-06T18:18:52.541218Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql_kfnp_yii2 | 2019-10-06T18:18:52.541230Z 0 [Note] InnoDB: Uses event mutexes
mysql_kfnp_yii2 | 2019-10-06T18:18:52.541238Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
mysql_kfnp_yii2 | 2019-10-06T18:18:52.541246Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
mysql_kfnp_yii2 | 2019-10-06T18:18:52.541254Z 0 [Note] InnoDB: Using Linux native AIO
mysql_kfnp_yii2 | 2019-10-06T18:18:52.541733Z 0 [Note] InnoDB: Number of pools: 1
mysql_kfnp_yii2 | 2019-10-06T18:18:52.542240Z 0 [Note] InnoDB: Using CPU crc32 instructions
mysql_kfnp_yii2 | 2019-10-06T18:18:52.545656Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
mysql_kfnp_yii2 | 2019-10-06T18:18:52.560108Z 0 [Note] InnoDB: Completed initialization of buffer pool
mysql_kfnp_yii2 | 2019-10-06T18:18:52.564822Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
mysql_kfnp_yii2 | 2019-10-06T18:18:52.611646Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
mysql_kfnp_yii2 | 2019-10-06 18:18:52 0x7f0262309740 InnoDB: Assertion failure in thread 139648214013760 in file ut0ut.cc line 910
mysql_kfnp_yii2 | InnoDB: We intentionally generate a memory trap.
mysql_kfnp_yii2 | InnoDB: Submit a detailed bug report to bugs.mysql.com.
mysql_kfnp_yii2 | InnoDB: If you get repeated assertion failures or crashes, even
mysql_kfnp_yii2 | InnoDB: immediately after the mysqld startup, there may be
mysql_kfnp_yii2 | InnoDB: corruption in the InnoDB tablespace. Please refer to
mysql_kfnp_yii2 | InnoDB: dev.mysql.com/doc/refman/5.7/en/forcing-innodb-rec...
mysql_kfnp_yii2 | InnoDB: about forcing recovery.
mysql_kfnp_yii2 | 18:18:52 UTC - mysqld got signal 6 ;
mysql_kfnp_yii2 | This could be because you hit a bug. It is also possible that this binary
mysql_kfnp_yii2 | or one of the libraries it was linked against is corrupt, improperly built,
mysql_kfnp_yii2 | or misconfigured. This error can also be caused by malfunctioning hardware.
mysql_kfnp_yii2 | Attempting to collect some information that could help diagnose the problem.
mysql_kfnp_yii2 | As this is a crash and something is definitely wrong, the information
mysql_kfnp_yii2 | collection process might fail.
mysql_kfnp_yii2 |
mysql_kfnp_yii2 | key_buffer_size=8388608
mysql_kfnp_yii2 | read_buffer_size=131072
mysql_kfnp_yii2 | max_used_connections=0
mysql_kfnp_yii2 | max_threads=151
mysql_kfnp_yii2 | thread_count=0
mysql_kfnp_yii2 | connection_count=0
mysql_kfnp_yii2 | It is possible that mysqld could use up to
mysql_kfnp_yii2 | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68196 K bytes of memory
mysql_kfnp_yii2 | Hope that's ok; if not, decrease some variables in the equation.
mysql_kfnp_yii2 |
mysql_kfnp_yii2 | Thread pointer: 0x0
mysql_kfnp_yii2 | Attempting backtrace. You can use the following information to find out
mysql_kfnp_yii2 | where mysqld died. If you see no messages after this, something went
mysql_kfnp_yii2 | terribly wrong...
mysql_kfnp_yii2 | stack_bottom = 0 thread_stack 0x40000
mysql_kfnp_yii2 | mysqld(my_print_stacktrace+0x2c)[0x558d8bdb7dcc]
mysql_kfnp_yii2 | mysqld(handle_fatal_signal+0x479)[0x558d8b6e2099]
mysql_kfnp_yii2 | /lib/x86_64-linux-gnu/libpthread.so.0(+0x110e0)[0x7f0261ee60e0]
mysql_kfnp_yii2 | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f0260672fff]
mysql_kfnp_yii2 | /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f026067442a]
mysql_kfnp_yii2 | mysqld(+0x62a713)[0x558d8b6b8713]
mysql_kfnp_yii2 | mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x558d8bf8864d]
mysql_kfnp_yii2 | mysqld(+0xfa73b1)[0x558d8c0353b1]
mysql_kfnp_yii2 | mysqld(+0xfa79e8)[0x558d8c0359e8]
mysql_kfnp_yii2 | mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x558d8c03eba0]
mysql_kfnp_yii2 | mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x558d8bff3c2e]
mysql_kfnp_yii2 | mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x558d8bfc2e6a]
mysql_kfnp_yii2 | mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x558d8bf66ab3]
mysql_kfnp_yii2 | mysqld(+0x629887)[0x558d8b6b7887]
mysql_kfnp_yii2 | mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x558d8bf3394d]
mysql_kfnp_yii2 | mysqld(+0xd70f08)[0x558d8bdfef08]
mysql_kfnp_yii2 | mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x558d8b72cf6f]
mysql_kfnp_yii2 | mysqld(+0xb16d66)[0x558d8bba4d66]
mysql_kfnp_yii2 | mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x558d8bba7f70]
mysql_kfnp_yii2 | mysqld(+0x64c79e)[0x558d8b6da79e]
mysql_kfnp_yii2 | mysqld(_Z11mysqld_mainiPPc+0xc71)[0x558d8b6dc361]
mysql_kfnp_yii2 | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f02606602e1]
mysql_kfnp_yii2 | mysqld(_start+0x2a)[0x558d8b6d2a3a]
mysql_kfnp_yii2 | The manual page at dev.mysql.com/doc/mysql/en/crashing.html contains
mysql_kfnp_yii2 | information that should help you find out what is causing the crash.
mysql_kfnp_yii2 exited with code 2

Моя конфигурация composer-compose.yml

version: '3'

services:
  webserver:
    container_name: apache-php_kfnp_yii2
    build:
      context: .
      dockerfile: ./docker/Dockerfile
    environment:
      XDEBUG_CONFIG: remote_host=host.docker.internal
      PHP_IDE_CONFIG: serverName=localhost
    ports:
    - 80:80
    volumes:
    - ./:/var/www
    links:
    - db
    depends_on:
    - db

  db:
    container_name: mysql_kfnp_yii2
    image: 'mysql:5.7'
    command: --default-authentication-plugin=mysql_native_password
    restart: always
    ports:
    - 9513:3306
    environment:
      MYSQL_ROOT_PASSWORD: password
      MYSQL_DATABASE: yii2basic
      MYSQL_USER: mysqluser
      MYSQL_PASSWORD: mysqluser
    volumes:
    - ./docker/database:/var/lib/mysql

Может кто-то пробовал ее решить? Писали что изменить данные в my.conf или my.ini хотя я не вижу такого файла.
Вот что хранит конфигурация mysql

Answer 1

[Игорь]

my.cnf

[mysqld]
explicit_defaults_for_timestamp = 1

Пожалуйста, синхронизируете "книжный том", я вас умоляю.
./docker/my.cnf:/etc/mysql/my.cnf

Comments

[chupasaurus]

s/объёмы/тома/

[Игорь]

chupasaurus, ???

[chupasaurus]

Игорь, Значения слова volume. В случае с docker — "книжный том" по аналогии с СХД.

[Игорь]

chupasaurus, К чему это?

[chupasaurus]

Игорь,

Синхронизируйте объёмы с
./docker/my.cnf:/etc/mysql/my.cnf

[Игорь]

chupasaurus, Я вас не понимаю.

[Игорь]

chupasaurus, Мы не на конкурсе "Знатный халиварщик"

[chupasaurus]

Игорь, правильно, мы на техническом ресурсе.

О сервисе
На «Тостере» можно получить ответ на вопрос по любой теме IT от участников сообщества, хорошо разбирающихся в этой теме.

Если вы так хорошо разбираетесь в теме, впредь называйте docker volume - громкостями.

[Игорь]

Уважаемы chupasaurus, я имел в виду "volumes"
Вы прекрасно поняли что я имел в виду.
И ТС понял.

Даже мой кот уже это понял.
А вам лишь бы по Клаве бахать.

Ок, буду употреблять "Пожалуйста синхронизируете книжный том"

[Игорь]

chupasaurus, Вы случаем не с Украины?

[Руслан Абсалямов]

А где мне его взять, я попытался так сделать мне ошибку выдала

ERROR: for mysql_kfnp_yii2  Cannot start service db: OCI runtime create failed: container_linux.go:345: starting container process caused "process_linux.go:430: container init caused \"rootfs_linux.go:58: mounting \\\"/Users/user/Sites/app/docker/database/my.cnf\\\" to rootfs \\\"/var/lib/docker/overlay2/63b0734fb625b7e14dbbddf528a2ed8b1c00f39241bfee251f9fa0a3ad7fb121/merged\\\" at \\\"/var/lib/docker/overlay2/63b0734fb625b7e14dbbddf528a2ed8b1c00f39241bfee251f9fa0a3ad7fb121/merged/etc/mysql/mysql.cnf\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for db  Cannot start service db: OCI runtime create failed: container_linux.go:345: starting container process caused "process_linux.go:430: container init caused \"rootfs_linux.go:58: mounting \\\"/Users/user/Sites/app/docker/database/my.cnf\\\" to rootfs \\\"/var/lib/docker/overlay2/63b0734fb625b7e14dbbddf528a2ed8b1c00f39241bfee251f9fa0a3ad7fb121/merged\\\" at \\\"/var/lib/docker/overlay2/63b0734fb625b7e14dbbddf528a2ed8b1c00f39241bfee251f9fa0a3ad7fb121/merged/etc/mysql/mysql.cnf\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
ERROR: Encountered errors while bringing up the project.

[Руслан Абсалямов]

Если просто создать файл и добавить строки которые нужно то у меня проблемы

mysql_kfnp_yii2 | 2019-10-13T09:02:22.723977Z 0 [Note] mysqld (mysqld 5.7.27) starting as process 1 ...
mysql_kfnp_yii2 | 2019-10-13T09:02:22.735574Z 0 [Note] InnoDB: PUNCH HOLE support available
mysql_kfnp_yii2 | 2019-10-13T09:02:22.735639Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql_kfnp_yii2 | 2019-10-13T09:02:22.735646Z 0 [Note] InnoDB: Uses event mutexes
mysql_kfnp_yii2 | 2019-10-13T09:02:22.735652Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
mysql_kfnp_yii2 | 2019-10-13T09:02:22.735656Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
mysql_kfnp_yii2 | 2019-10-13T09:02:22.735661Z 0 [Note] InnoDB: Using Linux native AIO
mysql_kfnp_yii2 | 2019-10-13T09:02:22.736297Z 0 [Note] InnoDB: Number of pools: 1
mysql_kfnp_yii2 | 2019-10-13T09:02:22.736585Z 0 [Note] InnoDB: Using CPU crc32 instructions
mysql_kfnp_yii2 | 2019-10-13T09:02:22.739217Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
mysql_kfnp_yii2 | 2019-10-13T09:02:22.750177Z 0 [Note] InnoDB: Completed initialization of buffer pool
mysql_kfnp_yii2 | 2019-10-13T09:02:22.752939Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
mysql_kfnp_yii2 | 2019-10-13T09:02:22.789180Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
mysql_kfnp_yii2 | 2019-10-13 09:02:22 0x7f40aa1e2740  InnoDB: Assertion failure in thread 139915708737344 in file ut0ut.cc line 910
mysql_kfnp_yii2 | InnoDB: We intentionally generate a memory trap.
mysql_kfnp_yii2 | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
mysql_kfnp_yii2 | InnoDB: If you get repeated assertion failures or crashes, even
mysql_kfnp_yii2 | InnoDB: immediately after the mysqld startup, there may be
mysql_kfnp_yii2 | InnoDB: corruption in the InnoDB tablespace. Please refer to
mysql_kfnp_yii2 | InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
mysql_kfnp_yii2 | InnoDB: about forcing recovery.
mysql_kfnp_yii2 | 09:02:22 UTC - mysqld got signal 6 ;
mysql_kfnp_yii2 | This could be because you hit a bug. It is also possible that this binary
mysql_kfnp_yii2 | or one of the libraries it was linked against is corrupt, improperly built,
mysql_kfnp_yii2 | or misconfigured. This error can also be caused by malfunctioning hardware.
mysql_kfnp_yii2 | Attempting to collect some information that could help diagnose the problem.
mysql_kfnp_yii2 | As this is a crash and something is definitely wrong, the information
mysql_kfnp_yii2 | collection process might fail.
mysql_kfnp_yii2 | 
mysql_kfnp_yii2 | key_buffer_size=8388608
mysql_kfnp_yii2 | read_buffer_size=131072
mysql_kfnp_yii2 | max_used_connections=0
mysql_kfnp_yii2 | max_threads=151
mysql_kfnp_yii2 | thread_count=0
mysql_kfnp_yii2 | connection_count=0
mysql_kfnp_yii2 | It is possible that mysqld could use up to 
mysql_kfnp_yii2 | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68196 K  bytes of memory
mysql_kfnp_yii2 | Hope that's ok; if not, decrease some variables in the equation.
mysql_kfnp_yii2 | 
mysql_kfnp_yii2 | Thread pointer: 0x0
mysql_kfnp_yii2 | Attempting backtrace. You can use the following information to find out
mysql_kfnp_yii2 | where mysqld died. If you see no messages after this, something went
mysql_kfnp_yii2 | terribly wrong...
mysql_kfnp_yii2 | stack_bottom = 0 thread_stack 0x40000
mysql_kfnp_yii2 | mysqld(my_print_stacktrace+0x2c)[0x55c7d93e6dcc]
mysql_kfnp_yii2 | mysqld(handle_fatal_signal+0x479)[0x55c7d8d11099]
mysql_kfnp_yii2 | /lib/x86_64-linux-gnu/libpthread.so.0(+0x110e0)[0x7f40a9dbf0e0]
mysql_kfnp_yii2 | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f40a854bfff]
mysql_kfnp_yii2 | /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f40a854d42a]
mysql_kfnp_yii2 | mysqld(+0x62a713)[0x55c7d8ce7713]
mysql_kfnp_yii2 | mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x55c7d95b764d]
mysql_kfnp_yii2 | mysqld(+0xfa73b1)[0x55c7d96643b1]
mysql_kfnp_yii2 | mysqld(+0xfa79e8)[0x55c7d96649e8]
mysql_kfnp_yii2 | mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x55c7d966dba0]
mysql_kfnp_yii2 | mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x55c7d9622c2e]
mysql_kfnp_yii2 | mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x55c7d95f1e6a]
mysql_kfnp_yii2 | mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x55c7d9595ab3]
mysql_kfnp_yii2 | mysqld(+0x629887)[0x55c7d8ce6887]
mysql_kfnp_yii2 | mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x55c7d956294d]
mysql_kfnp_yii2 | mysqld(+0xd70f08)[0x55c7d942df08]
mysql_kfnp_yii2 | mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x55c7d8d5bf6f]
mysql_kfnp_yii2 | mysqld(+0xb16d66)[0x55c7d91d3d66]
mysql_kfnp_yii2 | mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x55c7d91d6f70]
mysql_kfnp_yii2 | mysqld(+0x64c79e)[0x55c7d8d0979e]
mysql_kfnp_yii2 | mysqld(_Z11mysqld_mainiPPc+0xc71)[0x55c7d8d0b361]
mysql_kfnp_yii2 | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f40a85392e1]
mysql_kfnp_yii2 | mysqld(_start+0x2a)[0x55c7d8d01a3a]
mysql_kfnp_yii2 | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
mysql_kfnp_yii2 | information that should help you find out what is causing the crash.

[Игорь]

Руслан Абсалямов, Выкиньте вашу конфигурацию в топку, воспользуйтесь нормальным решением
Плиз.

# Database
  db:
    image: percona:latest
    container_name: project.db
    restart: on-failure
    ports:
      - 127.0.0.100:3306:3306
    expose:
      - 3306
    environment:
      - MYSQL_ROOT_PASSWORD=secret
      - MYSQL_DATABASE=mydatabase
      - MYSQL_ROOT_HOST=%

[Руслан Абсалямов]

Игорь, это получилось подключится докер к mysql в моем случае не работал, что есть в этом image, что нет в официальном mysql

[Руслан Абсалямов]

Просто свой я достал из официальной mysql docker hud

[Игорь]

Руслан Абсалямов, Это Percona и этим всё сказано.
Посмотрите здесь информацию