When Using docker-compose up mysql MySQL Doesn't Start
#1126
Comments
|
Quick update when I drop the MySQL down to version 5.7 it builds and functions properly. I'm not sure what step might be missing for me as the database should not exist as everything was cleared. Unless someone could point me in a direction regarding phantom databases in docker (just my lack of knowledge potentially). |
|
Just for clarity, did you rebuild mysql container with |
|
I've tried |
|
I have the same problem, and I use Docker Version 17.06.2-ce-win27 (13194) `WARNING: Image for service mysql was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`. Creating laradock_mysql_1 ... Creating laradock_mysql_1 ... done Attaching to laradock_mysql_1 mysql_1 | 2017-09-30T23:46:36.415592Z 0 [Note] Basedir set to /usr/ mysql_1 | 2017-09-30T23:46:36.415723Z 0 [Warning] The syntax '--symbolic-links/-s' is deprecated and will be removed in a future release mysql_1 | 2017-09-30T23:46:36.415752Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They w ill be merged with strict mode in a future release. mysql_1 | 2017-09-30T23:46:36.419196Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled mysql_1 | 2017-09-30T23:46:36.419233Z 0 [Note] /usr/sbin/mysqld (mysqld 8.0.3-rc-log) starting as process 1 ... mysql_1 | 2017-09-30T23:46:36.430072Z 0 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL se rver acts as a master and has his hostname changed!! Please use '--log-bin=441b44a5a18b-bin' to avoid this problem. mysql_1 | 2017-09-30T23:46:36.442964Z 0 [Note] InnoDB: Using Linux native AIO mysql_1 | 2017-09-30T23:46:36.443301Z 0 [Note] Plugin 'FEDERATED' is disabled. mysql_1 | 2017-09-30T23:46:36.445645Z 1 [ERROR] Failed to find valid data directory. mysql_1 | 2017-09-30T23:46:36.445903Z 0 [ERROR] Data Dictionary initialization failed. mysql_1 | 2017-09-30T23:46:36.445985Z 0 [ERROR] Aborting mysql_1 | 2017-09-30T23:46:36.446011Z 0 [Note] Binlog end mysql_1 | 2017-09-30T23:46:36.447956Z 0 [Note] Shutting down plugin 'InnoDB' mysql_1 | 2017-09-30T23:46:36.448022Z 0 [Note] Shutting down plugin 'MyISAM' mysql_1 | 2017-09-30T23:46:36.448058Z 0 [Note] Shutting down plugin 'CSV' mysql_1 | 2017-09-30T23:46:36.450846Z 0 [Note] /usr/sbin/mysqld: Shutdown complete mysql_1 | laradock_mysql_1 exited with code 1 ` |
|
Got similar issue after upgrade the laravel to 5.5, after run |
|
I solved this problem. This is because of data folder. I was running it using mysql 5.7 then abort it in the middle of building, and change the mysql to 8.0. here some explanation #1138 (comment) Try this step. Try remove the docker image. List all images using Then try |
|
@ganjarsetia solution worked. Thanks |
|
have same issue here have try solutions above, but not fix my problem |
|
I came here looking for a solution to the mysql container exiting when started. #1138 (comment) fixed this for me. Just leaving this here for anyone that comes here like me. This was one of the results when I literally Googled the error message. |
your solution is still work until 2019 |
|
Hi 👋 this issue has been automatically marked as |
|
In my case, i crash to mariadb data in ~/.laradock/data/mariadb so solution is remove or rename data folder and restart laradock Ref: https://devhoi.com/threads/laradock-on-mac-error-unknown-unsupported-storage-engine-innodb.28/ |
|
When we remove folder data, our data will be lost. So this is not a suitable solution |
|
In my case, I changed the e.g. I suspect this happened because I started a new project with laradock when I already had another project using laradock on my machine. There was already a mysql data folder from my other project stored at |
Still working in 2021 👍 |
|
this is completely related with data directory folder permissions and owners. |
Still working in 2022 :D |
this answer saved my day after 5 years |
Still works. Thank you |
Still working 2023 - in my case it occurred after I downgraded from MySQL8 to 5.7 |
|
How can I use this without losing the data? Removing the volume name will make me lose the data, doesn't it? So, what's the approach without data losing? Thanks. |
|
i have this kind of error. i already reinstall from the images to the docker |
and others
Info:
$ docker --version): Docker version 17.06.1-ce, build 874a737$ git rev-parse HEAD): 801ccd4Issue:
When running
docker-compose up mysqlthe container fails to start.Expected behavior:
The loading of mysql container.
Reproduce:
After updating from the git repo my mysql failed to start. I cleared my system of volumes, containers and images. I followed #1110 that solution to no avail.
Relevant Code:
The text was updated successfully, but these errors were encountered: