docker-composeでwordpressの開発環境を構築したが、英語になってしまう

docker-composeでwordpressの開発環境を構築し、wordpressの初期設定を行おうと思ったのですが、初期設定画面が英語になってしまい、以後wordpressのsettingsから言語を変えようと思っても日本語が候補にありません（そもそも候補が英語しかない）
このようになってしまう原因はdocker-dompose.ymlファイルにあるのかなと思ったのですが、
特にwordpressの環境設定に言語を設定する項目もなく、困っています。
もしくはOSやDBの言語に依存していたりするのでしょうか？

通常、最初に言語を選ぶ画面が現れるはずなのですが、それも出てこず、いきなりサイトのテーマの設定画面から始まります。

どなたかご教授いただけないでしょうか？よろしくお願いいたします。

docker
1version: '3'
2
3services:
4    db:
5        image: mysql:5.7
6        volumes:
7            - db_data:/var/lib/mysql
8        restart: always
9        environment:
10            MYSQL_ROOT_PASSWORD: root
11            MYSQL_DATABASE: wordpress
12            MYSQL_USER: wordpress
13            MYSQL_PASSWORD: wordpress
14
15    wordpress:
16        depends_on:
17            - db
18        image: wordpress:latest
19        volumes:
20            - ./wp-content:/var/www/html/wp-content
21        ports:
22            - "8080:80"
23        restart: always
24        environment:
25            WORDPRESS_DB_HOST: db:3306
26            WORDPRESS_DB_USER: wordpress
27            WORDPRESS_DB_PASSWORD: wordpress
28volumes:
29    db_data:

OS: ubuntu
docker: Docker version 19.03.12, build 48a66213fe
docker-compose: docker-compose version 1.26.2, build eefe0d31

行動規範の内容に同意します

回答1件

ベストアンサー

次のように bind マウントを変更し:

yaml
1     volumes:
2       - ./wp-content:/var/www/html/wp-content

↓

yaml
1     volumes:
2       - ./wordpress:/var/www/html

且つ、ホスト側にディレクトリーを作っていない状態で
docker-compose up すると、言語選択が表示されます

原因

WordPress の公式イメージは最初、
/var/www/html は空になっており、
ENTRYPOINT の処理で
WordPress のコードがドキュメントルートにデプロイされる仕組みになっています
参考: wordpress/docker-entrypoint.sh at master · docker-library/wordpress

yaml
1volumes:
2       - db_data:/var/lib/mysql

上記の bind マウントを行うと、docker-compose up を行うと、
デプロイに失敗します:

console
1$ docker-compose up
2Creating network "test-docker-compose_default" with the default driver
3Creating volume "test-docker-compose_db_data" with default driver
4Creating test-docker-compose_db_1 ... done
5Creating test-docker-compose_wordpress_1 ... done
6Attaching to test-docker-compose_db_1, test-docker-compose_wordpress_1
7db_1         | 2020-07-19 03:33:17+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.29-1debian9 started.
8db_1         | 2020-07-19 03:33:17+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
9db_1         | 2020-07-19 03:33:17+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.29-1debian9 started.
10db_1         | 2020-07-19 03:33:17+00:00 [Note] [Entrypoint]: Initializing database files
11db_1         | 2020-07-19T03:33:17.556858Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
12db_1         | 2020-07-19T03:33:17.844306Z 0 [Warning] InnoDB: New log files created, LSN=45790
13db_1         | 2020-07-19T03:33:17.925250Z 0 [Warning] InnoDB: Creating foreign key constraint system tables.
14wordpress_1  | WordPress not found in /var/www/html - copying now...
15wordpress_1  | WARNING: /var/www/html is not empty! (copying anyhow)
16wordpress_1  | tar: ./wp-content/themes/twentyseventeen: Cannot mkdir: No such file or directory
17db_1         | 2020-07-19T03:33:17.961174Z 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: 9613a600-c970-11ea-853e-0242ac1c0002.
18db_1         | 2020-07-19T03:33:17.973753Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
19wordpress_1  | tar: ./wp-content/themes/twentyseventeen: Cannot mkdir: No such file or directory
20wordpress_1  | tar: ./wp-content/themes/twentyseventeen/screenshot.png: Cannot open: No such file or directory
21wordpress_1  | tar: ./wp-content/themes/twentyseventeen: Cannot mkdir: No such file or directory
22wordpress_1  | tar: ./wp-content/themes/twentyseventeen/page.php: Cannot open: No such file or directory
23wordpress_1  | tar: ./wp-content/themes/twentyseventeen: Cannot mkdir: No such file or directory
24wordpress_1  | tar: ./wp-content/themes/twentyseventeen/footer.php: Cannot open: No such file or directory
25wordpress_1  | tar: ./wp-content/themes/twentyseventeen: Cannot mkdir: No such file or directory
26wordpress_1  | tar: ./wp-content/themes/twentyseventeen/rtl.css: Cannot open: No such file or directory
27wordpress_1  | tar: ./wp-content/themes/twentyseventeen: Cannot mkdir: No such file or directory
28wordpress_1  | tar: ./wp-content/themes/twentyseventeen/search.php: Cannot open: No such file or directory
29db_1         | 2020-07-19T03:33:20.264375Z 0 [Warning] CA certificate ca.pem is self signed.
30db_1         | 2020-07-19T03:33:20.932808Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
31wordpress_1  | tar: Exiting with failure status due to previous errors