Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Mysql container working on Docker v17.12.0 but not on v18.01.0 #1584
I'm using Docker ToolBox on Windows10 and created 2 docker-machines :
On the same directory I execute docker-compose up and there is only an error on the machine with v18.01.0-ce.
The error appears on a mysql container using the image : mysql:5.6.
Do you have any ideas why it's happening ?
Getting this issue now with Docker Toolbox. Never encountered this before with Docker for Windows. Had to switch to Toolbox, as Docker of Windows stopped working due to Windows Updates. I've tried v17.12.0, yields the same issues. Would be glad to know how you resolved this @manonwbat
Hey all, I haven't gotten this working yet, so take with a grain of salt.
I didn't realise that /etc/mysql/conf.d/*.cnf would override the default /etc/mysql/my.cnf.
I'm now running into:
"[Warning] World-writable config file '/etc/mysql/conf.d/noaio.cnf' is ignored.
So, QQ, permissions are too broad.
So I assume once I define my own MySQL dockerfile, I should get this working.
Can't get the chmod to work lol :[
Appending to /etc/mysql.cnf instead - hate everything about this solution though.
Okay appending to /etc/mysql.cnf worked.
"Can't start server : Bind on unix socket: Operation not permitted"
I'm probably going leave it there... sounds like I'm just going to be perpetually pulling teeth with the lack of permissions. Open to suggestions though.