version: '2'
services:
    mysql:
        image: mysql:5.7.15
        ports:
            - 3306:3306
        volumes:
            - "./.data/db:/var/lib/mysql"
        environment:
            MYSQL_ROOT_PASSWORD: ${MYSQL_ROOT_PASSWORD}
            MYSQL_DATABASE: ${MYSQL_DATABASE}
            MYSQL_USER: ${MYSQL_USER}
            MYSQL_PASSWORD: ${MYSQL_PASSWORD}
        build: docker/php7-fpm
        ports:
            - 9000:9000
        links:
            - mysql:synthesizer
        volumes:
            - ${SYMFONY_APP_PATH}:/var/www/symfony
            - ./logs/symfony:/var/www/symfony/app/logs
    nginx:
        build: docker/nginx
        ports:
            - 80:80
        links:
            - php
        volumes_from:
            - php
        volumes:
            - ./logs/nginx/:/var/log/nginx
[docker logs]
mysql:5.7.15        "docker-entrypoint.sh"   14 seconds ago      Exited (1) 14 seconds ago
Initializing database
mysqld: Can't create/write to file '/var/lib/mysql/is_writable' (Errcode: 13 - Permission denied)
2016-10-05T04:26:41.741277Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-10-05T04:26:41.749972Z 0 [ERROR] --initialize specified but the data directory exists and is not writable. Aborting.
2016-10-05T04:26:41.750014Z 0 [ERROR] Aborting
          
@yosifkit I'm also experiencing this issue. Where would you specify the user: 1000:50. I assumed as a child of the mysql: image definition but htis is indicating it is invalid as it should be a string
services:
  wp_db:
    user: 1000:50
This is the output I get when I try to bring it up:
MacBook-Pro:wordpress-site brooney$ docker-compose up
ERROR: The Compose file './docker-compose.yml' is invalid because: services.wp_db.user contains an invalid type, it should be a string
      laradoc_mysql container fails to start: '/var/lib/mysql/is_writable' (Errcode: 13 - Permission denied)
      laradock/laradock#1134
          
Hello @yosifkit, I know it's an old issue but your fix doesn't seem to work for me. It did copy everything inside my volume (on my host), but this time I get another error : 2019-05-31T18:55:22.990012Z 1 [ERROR] [MY-012592] [InnoDB] Operating system error number 22 in a file operation.. Then my container stops running.
          
@tofl, that sounds like you might need something like MariaDB/mariadb-docker#200 (comment)
i.e. docker run -d -v /host/path/:/var/lib/mysql  mysql:8.0 --innodb-flush-method=O_DSYNC
I can't remember what is required to make it work (or if it will ever work), and it depends whether you are using Docker for Mac, Docker for Windows, or Boot2Docker (via Docker Toolbox).
In the future, it'd be better to post questions like this in the Docker Community Forums, the Docker Community Slack, or Stack Overflow.
          
If anyone else runs into this I was having the same problem but I didn't see the lines above this error which said:
db_1         | 2021-04-14T07:15:05.694499Z 0 [Warning] InnoDB: Retry attempts for writing partial data failed.
db_1         | 2021-04-14T07:15:05.694574Z 0 [ERROR] InnoDB: Write to file ./ibdata1failed at offset 0, 1048576 bytes should have been written, only 0 were written. Operating system error number 28. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
db_1         | 2021-04-14T07:15:05.694600Z 0 [ERROR] InnoDB: Error number 28 means 'No space left on device'
db_1         | 2021-04-14T07:15:05.694614Z 0 [ERROR] InnoDB: Could not set the file size of './ibdata1'. Probably out of disk space
I just had to increase the size of my Docker disk in OSX