Skip to content
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

Add troubleshooting note about host-mapped volume issue with MariaDB #5

Merged
merged 3 commits into from
Feb 14, 2020

Conversation

arobert3434
Copy link

Added note to README troubleshooting section about MariaDB startup with host-mapped data volume on Windows or Mac. (Try to save some investigation time for those hitting it.)

@j1cs
Copy link
Owner

j1cs commented Feb 14, 2020

Perfect. Also I would like if you can specify the workaround that works for you? You can put the link of the previous thread or wrote by you.
Thanks.

@arobert3434
Copy link
Author

In my case I used a named but not mapped volume ( ... -v MY_NAME:/var/lib/mysql ...). I added a bit of clarification to the doc, but then realized the issue and fix are reported against MariaDB's own container, which is not used here. It might be you can add the argument --innodb-flush-method=fsync in your MySQL startup and/or try some of the other suggestions in the issue thread and it will fix it. But that might hurt performance on Linux hosts.

@j1cs j1cs merged commit 11f8112 into j1cs:master Feb 14, 2020
@j1cs
Copy link
Owner

j1cs commented Feb 14, 2020

Perfect. Merged!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants