-
-
Notifications
You must be signed in to change notification settings - Fork 580
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom mysql / mariadb cnf file prevent container restart #1541
Comments
Thanks for this report, somebody noticed that and pointed out in slack the other day, maybe you. The very simple workaround is use the superior I still think we should fix this. |
One mitigating factor is that as things look right now, in the next release, |
I can confirm that this error happens under the same versions of MacOS, docker and docker-compose as above when using It seems to be some sort of file permission issue as the log shows following:
|
When providing custom mysql configuration in :
.ddev/mysql/myconf.cnf
The file is used on first start, but when you stop+start / restart ddev, the db container can't start cause it's unable to overwrite the custom file.
If you connect db container :
ddev ssh --service=db
and try to list mysql conf.d directory you will notice the file in 444 mode :
ls -al /etc/mysql/conf.d/myconf.cnf
will output (for example) :
-r--r--r-- 1 uid_501 gid_20 175 Apr 17 08:31 myconf.cnf
Steps to reproduce the behavior:
Version and configuration information (please complete the following information):
The text was updated successfully, but these errors were encountered: