docker mysql容器启动不_MySQL容器无法在Docker Compose中运行初始化脚本

红太狼 2022-11-03 05:52 215阅读 0赞

我在让我的MySQL容器运行来自Docker Compose的一些初始化脚本(创建一些数据库)时遇到问题。根据Docker

Hub上的文档，我将.sql文件挂载在其中，/docker-entrypoint-initdb.d但无济于事。

我的撰写文件如下：

version: '2'

services:

database:

image: mysql

ports:

\- "3307:3306"

environment:

MYSQL\_ROOT\_PASSWORD: root

volumes:

\- ./scripts/db:/docker-entrypoint-initdb.d

myservice:

image: company/myservice

expose:

\- "10001"

depends\_on:

\- database

links:

\- database

environment:

SERVICE\_PORT: 10001

DATABASE\_URL: jdbc:mysql://database:3306/myservice?autoReconnect=true&useSSL=false&characterEncoding=UTF-8

的内容./scripts/db只有1个文件init-databases.sql：

CREATE DATABASE myservice;

一旦启动，MySQL正在运行，但未创建数据库。服务容器还成功链接到MySQL容器。扑向MySQL容器；初始化脚本已成功安装在正确的位置。

有人可以在这里看到一些明显的问题吗？

撰写日志

database\_1 | 2016-04-01T05:35:55.020279Z 0 \[Note\] mysqld (mysqld 5.7.11) starting as process 1 ...

database\_1 | 2016-04-01T05:35:55.023277Z 0 \[Note\] InnoDB: PUNCH HOLE support available

database\_1 | 2016-04-01T05:35:55.023305Z 0 \[Note\] InnoDB: Mutexes and rw\_locks use GCC atomic builtins

database\_1 | 2016-04-01T05:35:55.023316Z 0 \[Note\] InnoDB: Uses event mutexes

database\_1 | 2016-04-01T05:35:55.023324Z 0 \[Note\] InnoDB: GCC builtin \_\_atomic\_thread\_fence() is used for memory barrier

database\_1 | 2016-04-01T05:35:55.023332Z 0 \[Note\] InnoDB: Compressed tables use zlib 1.2.8

database\_1 | 2016-04-01T05:35:55.023344Z 0 \[Note\] InnoDB: Using Linux native AIO

database\_1 | 2016-04-01T05:35:55.023491Z 0 \[Note\] InnoDB: Number of pools: 1

database\_1 | 2016-04-01T05:35:55.023566Z 0 \[Note\] InnoDB: Using CPU crc32 instructions

database\_1 | 2016-04-01T05:35:55.028689Z 0 \[Note\] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M

database\_1 | 2016-04-01T05:35:55.041026Z 0 \[Note\] InnoDB: Completed initialization of buffer pool

database\_1 | 2016-04-01T05:35:55.047324Z 0 \[Note\] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

database\_1 | 2016-04-01T05:35:55.061537Z 0 \[Note\] InnoDB: Highest supported file format is Barracuda.

database\_1 | 2016-04-01T05:35:55.076895Z 0 \[Note\] InnoDB: Creating shared tablespace for temporary tables

database\_1 | 2016-04-01T05:35:55.076987Z 0 \[Note\] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...

database\_1 | 2016-04-01T05:35:55.095683Z 0 \[Note\] InnoDB: File './ibtmp1' size is now 12 MB.

database\_1 | 2016-04-01T05:35:55.096484Z 0 \[Note\] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.

database\_1 | 2016-04-01T05:35:55.096540Z 0 \[Note\] InnoDB: 32 non-redo rollback segment(s) are active.

database\_1 | 2016-04-01T05:35:55.096931Z 0 \[Note\] InnoDB: Waiting for purge to start

database\_1 | 2016-04-01T05:35:55.147986Z 0 \[Note\] InnoDB: 5.7.11 started; log sequence number 11992841

database\_1 | 2016-04-01T05:35:55.148204Z 0 \[Note\] Plugin 'FEDERATED' is disabled.

database\_1 | 2016-04-01T05:35:55.149262Z 0 \[Note\] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.

database\_1 | 2016-04-01T05:35:55.149443Z 0 \[Warning\] CA certificate ca.pem is self signed.

database\_1 | 2016-04-01T05:35:55.150272Z 0 \[Note\] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib\_buffer\_pool

database\_1 | 2016-04-01T05:35:55.151068Z 0 \[Note\] InnoDB: Buffer pool(s) load completed at 160401 5:35:55

database\_1 | 2016-04-01T05:35:55.152775Z 0 \[Note\] Server hostname (bind-address): '\*'; port: 3306

database\_1 | 2016-04-01T05:35:55.154441Z 0 \[Note\] IPv6 is available.

database\_1 | 2016-04-01T05:35:55.154553Z 0 \[Note\] - '::' resolves to '::';

database\_1 | 2016-04-01T05:35:55.154571Z 0 \[Note\] Server socket created on IP: '::'.

database\_1 | 2016-04-01T05:35:55.156680Z 0 \[Warning\] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.

database\_1 | 2016-04-01T05:35:55.156738Z 0 \[Warning\] 'proxies\_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.

database\_1 | 2016-04-01T05:35:55.158280Z 0 \[Warning\] 'tables\_priv' entry 'sys\_config mysql.sys@localhost' ignored in --skip-name-resolve mode.

database\_1 | 2016-04-01T05:35:55.165273Z 0 \[Note\] Event Scheduler: Loaded 0 events

database\_1 | 2016-04-01T05:35:55.173462Z 0 \[Note\] mysqld: ready for connections.

database\_1 | Version: '5.7.11' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server (GPL)

docker mysql容器启动不_MySQL容器无法在Docker Compose中运行初始化脚本

发表评论取消回复

还没有评论，来说两句吧...

相关阅读

相关 Docker容器（五）Docker Compose

相关本地制作mysql镜像并在docker中启动容器

相关【Docker-compose容器编排】

相关 docker mysql容器启动不_MySQL容器无法在Docker Compose中运行初始化脚本

相关 linux下docker启动mysql容器

相关 Docker mysql容器修改配置文件后无法启动

相关 Docker MySQL 容器备份启动

相关 Docker 退出容器不停止容器运行

相关 Docker容器运行、连接MySQL镜像

相关 docker更改mysql配置文件后，无法启动mysql容器