Expected behavior
I would like to store data of mariadb container in my projet directory ./data
I put a volume in my docker-compose.yml
volumes:
- ./data:/var/lib/mysql
I expect to have my container work but it failed during creating db while container init.
Actual behavior
When I launch my container without volume, everything works. But if I put a volume it failed. It writes somes files and stopped.
2016-07-01 21:11:28 139973248370624 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2016-07-01 21:11:28 139973248370624 [Note] InnoDB: Database physically writes the file full:
2016-07-01 21:11:28 7f4e0fbf47c0 InnoDB: Error: Write to file ./ibdata1 failed at offset 0.
Information
Windows 10
Latest version of docker beta for Windows
A diagnostic was uploaded with id: 082520B7-F1C0-4761-9A1B-4DB51F78851D/2016-07-01_23-22-24
Steps to reproduce the behavior
My test is realy simple to reproduct. Here is my docker-compose.yml
I put it in => D:\Dev\lbcd_wp
wordpress:
image: wordpress
volumes:
- ./wp-content/:/var/www/html/wp-content
environment:
- WORDPRESS_DB_PASSWORD=example
links:
- db:mysql
ports:
- â80:80â
db:
image: mariadb
environment:
MYSQL_ROOT_PASSWORD: example
volumes:
- ./data:/var/lib/mysql
Launch docker-compose up
If I remove volumes everything is fine. But with my volume it writes some files :
- directory ./data/mysql (empty)
- aria_log.00000001 (16 Ko)
- aria_log_control (1 Ko)
- ibdata1 (0 ko)
and failed to start container
Error on console is:
2016-07-01 21:26:48 140044960102336 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2016-07-01 21:26:48 140044960102336 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2016-07-01 21:26:48 140044960102336 [Note] InnoDB: Database physically writes the file full: waitâŠ
2016-07-01 21:26:48 7f5ec21977c0 InnoDB: Error: Write to file ./ibdata1 failed at offset 0.
InnoDB: 1048576 bytes should have been written, only 0 were written.
InnoDB: Operating system error number 22.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 22 means âInvalid argumentâ.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2016-07-01 21:26:48 140044960102336 [ERROR] InnoDB: Error in creating ./ibdata1: probably out of disk space
Of course Iâm not out of space.
What is realy suprising it that it works without volume binding indicated. So auto binding work.
Thanks for your help