Docker-Maria DB不会启动

Docker-Maria DB不会启动,docker,docker-compose,mariadb,dockerfile,Docker,Docker Compose,Mariadb,Dockerfile,我有一台Windows10Pro电脑 我的docker compose文件中有以下内容 database: image: mariadb:5.5.57 ports: - "3306:3306" volumes: - ./sql/:/docker-entrypoint-initdb.d/ - ./data:/var/lib/mysql environment: - MYSQL_ROOT_PASSWORD=root - MYSQL_USER=rootUsr - MYSQL

我有一台Windows10Pro电脑

我的docker compose文件中有以下内容

  database:
image: mariadb:5.5.57
ports:
  - "3306:3306"
volumes:
  - ./sql/:/docker-entrypoint-initdb.d/
  - ./data:/var/lib/mysql
environment:
  - MYSQL_ROOT_PASSWORD=root
  - MYSQL_USER=rootUsr
  - MYSQL_PASSWORD=rootPwd
  - MYSQL_DATABASE=root_db
当我运行docker compose up时,我在控制台中得到这个错误

 database_1     | InnoDB: 0 pages (rounded down to MB) than specified in the .cnf file:
database_1     | InnoDB: initial 640 pages, max 0 (relevant if non-zero) pages!
database_1     | 180324 17:12:47 InnoDB: Could not open or create data files.
database_1     | 180324 17:12:47 InnoDB: If you tried to add new data files, and it failed here,
database_1     | 180324 17:12:47 InnoDB: you should now edit innodb_data_file_path in my.cnf back
database_1     | 180324 17:12:47 InnoDB: to what it was, and remove the new ibdata files InnoDB created
consumer_1     | Starting the development server...
database_1     | 180324 17:12:47 InnoDB: in this failed attempt. InnoDB only wrote those files full of
database_1     | 180324 17:12:47 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
database_1     | 180324 17:12:47 InnoDB: remove old data files which contain your precious data!
database_1     | 180324 17:12:47 [ERROR] Plugin 'InnoDB' init function returned error.
database_1     | 180324 17:12:47 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
database_1     | 180324 17:12:47 [Note] Plugin 'FEEDBACK' is disabled.
database_1     | 180324 17:12:47 [ERROR] Unknown/unsupported storage engine: InnoDB
database_1     | 180324 17:12:47 [ERROR] Aborting
我还需要做些什么才能让maria db在docker中运行吗

更新
我已尝试删除所有卷并进行重建,但仍然出现与下面相同的错误

从撰写文件中删除了卷,效果良好。 更新
在Amazon EC2实例上尝试了相同的docker compose文件,第一次删除卷时效果很好,您有一些“坏”文件或@Mazel的权限问题,删除了所有卷并重建了,但仍然得到上面突出显示的问题,我的意思是从compose文件中删除它们。如果我在没有它们的情况下尝试你的代码,它就会工作。所以这一定很有趣-我刚刚删除了数据卷,它现在正在工作。权限问题?您是否阅读了您在此处发布的错误?:-)你可以用它来修理