You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Without this wrapper script, mysql does not have write access to the host volume:
Attaching to piwik_db_1, piwik_app_1, piwik_web_1, piwik_cron_1
db_1 | Initializing database
db_1 | 2016-05-17T08:40:43.947123Z 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
app_1 | [17-May-2016 08:39:56] NOTICE: fpm is running, pid 1
app_1 | [17-May-2016 08:39:56] NOTICE: ready to handle connections
db_1 | 2016-05-17T08:40:43.981323Z 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
db_1 | 2016-05-17T08:40:43.981347Z 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
db_1 | 2016-05-17T08:40:43.981351Z 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
db_1 | 2016-05-17T08:40:43.981353Z 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
db_1 | 2016-05-17T08:40:43.981355Z 0 [ERROR] InnoDB: Cannot open datafile './ibdata1'
db_1 | 2016-05-17T08:40:43.981358Z 0 [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!
db_1 | 2016-05-17T08:40:43.981361Z 0 [ERROR] InnoDB: InnoDB Database creation was aborted with error Cannot open a file. You may need to delete the ibdata1 file before trying to start up again.
db_1 | 2016-05-17T08:40:44.583103Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
db_1 | 2016-05-17T08:40:44.583129Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
db_1 | 2016-05-17T08:40:44.583135Z 0 [ERROR] Failed to initialize plugins.
db_1 | 2016-05-17T08:40:44.583137Z 0 [ERROR] Aborting
The text was updated successfully, but these errors were encountered:
This is a know issue. The current workaround is to use a wrapper script around mysql's entrypoint
Without this wrapper script, mysql does not have write access to the host volume:
The text was updated successfully, but these errors were encountered: