Not working with docker-compose and mounted volumes on WSL/Windows 10

[nowox]

I have this folder

$ tree
.
├── db
└── docker-compose.yml

And this configuration:

version: "2"
services:
  mysql:
    image: mysql:8.0
    ports:
      - "3306"
    volumes:
      - ./db:/var/lib/mysql
    environment:
      MYSQL_ALLOW_EMPTY_PASSWORD: 1

On this machine:

Linux CE589LT 4.4.0-17134-Microsoft #345-Microsoft Wed Sep 19 17:47:00 PST 2018 x86_64 x86_64 x86_64 GNU/Linux
Docker version 18.06.1-ce, build e68fc7a
docker-compose version 1.17.1, build unknown

If I do:

docker-compose up

I get this error:

Initializing database
2018-12-07T12:31:55.351428Z 0 [Warning] [MY-011070] [Server] 'Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it' is deprecated and will be removed in a future release.
2018-12-07T12:31:55.351566Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 8.0.13) initializing of server in progress as process 28
2018-12-07T12:32:02.860551Z 5 [Warning] [MY-010453] [Server] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
2018-12-07T12:32:05.304342Z 5 [Warning] [MY-010315] [Server] 'user' entry 'mysql.infoschema@localhost' ignored in --skip-name-resolve mode.
2018-12-07T12:32:05.304417Z 5 [Warning] [MY-010315] [Server] 'user' entry 'mysql.session@localhost' ignored in --skip-name-resolve mode.
2018-12-07T12:32:05.304432Z 5 [Warning] [MY-010315] [Server] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.
2018-12-07T12:32:05.304443Z 5 [Warning] [MY-010315] [Server] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.
2018-12-07T12:32:05.304469Z 5 [Warning] [MY-010323] [Server] 'db' entry 'performance_schema mysql.session@localhost' ignored in --skip-name-resolve mode.
2018-12-07T12:32:05.304488Z 5 [Warning] [MY-010323] [Server] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
2018-12-07T12:32:05.304500Z 5 [Warning] [MY-010311] [Server] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
2018-12-07T12:32:05.304612Z 5 [Warning] [MY-010330] [Server] 'tables_priv' entry 'user mysql.session@localhost' ignored in --skip-name-resolve mode.
2018-12-07T12:32:05.304634Z 5 [Warning] [MY-010330] [Server] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
2018-12-07T12:32:06.608964Z 0 [System] [MY-013170] [Server] /usr/sbin/mysqld (mysqld 8.0.13) initializing of server has completed
Database initialized
MySQL init process in progress...
2018-12-07T12:32:08.991973Z 0 [Warning] [MY-011070] [Server] 'Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it' is deprecated and will be removed in a future release.
2018-12-07T12:32:08.992089Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.13) starting as process 79
2018-12-07T12:32:09.169130Z 1 [ERROR] [MY-012592] [InnoDB] Operating system error number 2 in a file operation.
2018-12-07T12:32:09.169207Z 1 [ERROR] [MY-012593] [InnoDB] The error means the system cannot find the path specified.
2018-12-07T12:32:09.169221Z 1 [ERROR] [MY-012594] [InnoDB] If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2018-12-07T12:32:09.169232Z 1 [ERROR] [MY-012646] [InnoDB] File ./ibdata1: 'open' returned OS error 71. Cannot continue operation
2018-12-07T12:32:09.169241Z 1 [ERROR] [MY-012981] [InnoDB] Cannot continue operation.
MySQL init process in progress...
MySQL init process in progress...
MySQL init process in progress...

[...]

MySQL init process in progress...
MySQL init process in progress...
MySQL init process in progress...
MySQL init process failed.

If I remove the volume from my docker-compose it works...

What is the problem?

I have tried this from both WSL and PowerShell

[wglambert]

File ./ibdata1: 'open' returned OS error 71.

What are your permissions on the volume?

[nowox]

777 because the volume on WSL was on a windows mount (/mnt/c/users/...)

[wglambert]

From what I can find, people that encounter this error have an incorrect datadir path in the my.cnf, I'm thinking it's some sort of incompatibility with WSL.
There's nothing we can change in the image to remedy this so the best I can recommend is asking over at a windows LCOW/WSL forum/issue-tracker or the Docker Community Forums, the Docker Community Slack, or Stack Overflow

You could also use a docker named volume as it uses AUFS/Overlay2 as the storage driver

[mabdelfattah]

I have the same problem, the weird thing is, I tried to cat the user.MYD and I got the following error, although the file is there! and I can see it when I ls!

cat: /var/lib/mysql/mysql/user.MYD: No such file or directory

So, I assume it is a problem with Docker itself, but why only .MYD and .MYD files? I can cat db.opt and .frm files without any issues.

[mabdelfattah]

@wglambert It works with docker volumes (without mounting)

mysql:
  volumes:
    - my_docker_volume:/var/lib/mysql

volumes:
  my_docker_volume: #no driver, not type, etc.

Any idea how can I take backup of this docker-volume in case I want to use it on a different machine later? Also, do you know if I can specify the volume path?

[nowox]

I have managed to make it work using persistent. This is actually a better option I think.

  db:
    image: mysql:8.0
    command: --default-authentication-plugin=mysql_native_password
    restart: always
    ports:
      - 3306:3306
    environment:
      MYSQL_ROOT_PASSWORD: secret
    volumes:
        - ./dump.sql:/docker-entrypoint-initdb.d/dump.sql
        - persistent:/var/lib/mysql

[tianon]

I think this is technically the same issue as MariaDB/mariadb-docker#95 and docker-library/percona#42.

[tianon]

(And thus, not something we can fix in the image, and something that'd be more appropriately discussed further on the Docker Community Forums, the Docker Community Slack, or Stack Overflow.)