Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- If you have this error
- 2017-05-03 15:11:06 140715339528128 [ERROR] InnoDB: Error in creating ./ibdata1: probably out of disk space
- 2017-05-03 15:11:06 140715339528128 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
- 2017-05-03 15:11:06 140715339528128 [ERROR] Plugin 'InnoDB' init function returned error.
- 2017-05-03 15:11:06 140715339528128 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
- 2017-05-03 15:11:06 140715339528128 [ERROR] Unknown/unsupported storage engine: InnoDB
- 2017-05-03 15:11:06 140715339528128 [ERROR] Aborting
- Then you need to add this code in docker-compose.yml
- Section with db
- Code for MariaDB: command: --innodb-flush-method=O_DSYNC --innodb-use-native-aio=0 --log_bin=ON
- Code for MySQL: command: --innodb_use_native_aio=0
- Example:
- version: '3.1'
- services:
- db:
- image: mariadb
- restart: always
- environment:
- MYSQL_ROOT_PASSWORD: 123
- command: --innodb-flush-method=O_DSYNC --innodb-use-native-aio=0 --log_bin=ON
- volumes:
- - ./data:/var/lib/mysql
- ports:
- - "3306:3306"
- Good luck:)
Add Comment
Please, Sign In to add comment