-
-
Notifications
You must be signed in to change notification settings - Fork 654
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
mysql 5.6 cnf file don't work #373
Comments
im trying to add |
@jlopezjuy I am really stuck on this one. Debian here as well and it works like a charm. |
@jlopezjuy did you encounter any errors on file permissions. This file is NOT READ if it has the wrong permissions. See here: https://devilbox.readthedocs.io/en/latest/support/troubleshooting.html#warning-world-writable-config-file-etc-mysql-docker-default-d-my-cnf-is-ignored |
Stale issue This issue was marked with Beep beep, I am a bot - do not reply to me. |
I will close this issue as the requested information was not provided and I was unable to reproduce it. Feel free to reply here for re-opening. |
With last version (commit 3cbbdb3)
SUMMARY i have created cnf file on file contents: mysql info, lower lower_case_table_names is always 0 |
@manzolo I've reproduced the behaviour and identified the issue: The currently mounted config directory does not evaluate in any of the official MySQL images. The fix will be provided shortly. CC @jlopezjuy |
Fix will be available today. I've also added regression tests so that this issue won't be able to occur again: |
Fix is merged and available. Update all your MySQL, MariaDB and Percona images. The next Devilbox Bugfix release will also enforce this new version even though if you haven't explicitly pulled those images. |
Has been properly addressed in Release v1.0.1 |
SUMMARY
i have created cnf file on /devilbox/cfg/mysql-5.6/devilbox-custom.cnf
this fila contain
[mysqld]
lower_case_table_names=1
seeing mysql info, lower case table name is 0
STEPS TO REPRODUCE
created file, then run docker-compose up -d
The text was updated successfully, but these errors were encountered: