socket directory permission fix if volume #367
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
perhaps should be extended to config directory too (#368) |
|
Actually I shouldn't change subdirectories. |
The socket directory may be a volume with its ownership being that of root. This correct that ownership to be of user mysql to facilitate it starting. Thanks Douglas Silva for the bug report. closes #363.
grooverdan
force-pushed
the
issue-363-socket-permissions-in-volume
branch
from
80ce538 to
c1a03e1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The socket directory may be a volume with
its ownership being that of root.
This correct that ownership to be of user mysql
to facilitate it starting.
Thanks @o-alquimista for the bug report.
closes #363.