WSL2 + Docker Desktop pour Windows ne lance pas uniquement le conteneur MySQL

Seul MySQL n'a pas démarré avec docker

Plus précisément, si vous essayez de lancer divers conteneurs avec docker-compose up -d avec ** WSL2 + Docker Desktop pour Windows (+ Docker Compose) **, uniquement ** conteneur MySQL (dernière version de 5.7) Ne s'est pas levé **

# docker-compose ps
            Name                           Command               State            Ports
------------------------------------------------------------------------------------------------
test-_back_1        /wait-for-it.sh mysql-db ...   Up       0.0.0.0:8080->8080/tcp
test-_front_1       /bin/sh -c envsubst '$$TES ...   Up       0.0.0.0:3000->80/tcp
test-_mysql-db_1   docker-entrypoint.sh mysqld      Exit 1

Jetez un œil au journal

Vérifiez les journaux avec docker-compose logs -f

log

mysql-db_1  | 2020-10-17 02:54:50+09:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.31-1debian10 started.
mysql-db_1  | 2020-10-17 02:54:50+09:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
mysql-db_1  | 2020-10-17 02:54:50+09:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.31-1debian10 started.
mysql-db_1  | 2020-10-17 02:54:50+09:00 [Note] [Entrypoint]: Initializing database files
mysql-db_1  | mysqld: [Warning] World-writable config file '/etc/mysql/conf.d/my.cnf' is ignored.
mysql-db_1  | 2020-10-16T17:54:50.236065Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysql-db_1  | 2020-10-16T17:54:50.243510Z 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
mysql-db_1  | 2020-10-16T17:54:50.984126Z 0 [Warning] InnoDB: New log files created, LSN=****
mysql-db_1  | 2020-10-16T17:54:51.113491Z 0 [Warning] InnoDB: Creating foreign key constraint system tables.
mysql-db_1  | 2020-10-16T17:54:51.128211Z 0 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: ********
mysql-db_1  | 2020-10-16T17:54:51.133628Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
mysql-db_1  | mysqld: Can't change permissions of the file 'ca-key.pem' (Errcode: 1 - Operation not permitted)
mysql-db_1  | 2020-10-16T17:54:51.184562Z 0 [ERROR] Could not set file permission for ca-key.pem
mysql-db_1  | 2020-10-16T17:54:51.184583Z 0 [ERROR] Aborting
mysql-db_1  |

et enfin

mysql-db_1  | 2020-10-16T17:54:51.184562Z 0 [ERROR] Could not set file permission for ca-key.pem
mysql-db_1  | 2020-10-16T17:54:51.184583Z 0 [ERROR] Aborting

C'est gros

Solutions

Lorsque j'ai cherché sur Google, j'ai trouvé le problème suivant

• [WSL2] Permissions problem with mounted windows volume · Issue #4824 · docker/for-win

Quand je l'ai regardé, il y a eu une réponse disant que cela fonctionnait quand je suis passé de ** mysql: 5.7 ** à ** mysql: 5.7.16 **, donc quand j'ai changé la version, cela a commencé à fonctionner. (Dans mon cas, j'ai écrit la version de MySQL dans docker-compose.yml, donc je l'ai changée)

fin

――Est-ce lié à l'autorité de monter? Il semble que, mais je suis d'accord avec cela car je peux me déplacer localement pour le moment