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

Container fails to start if log-bin is used with writeable datadir #113

Closed
ltangvald opened this issue Oct 26, 2015 · 4 comments
Closed

Comments

@ltangvald
Copy link
Collaborator

If the user specifies a custom config that enabled binary logging, and the mysql user has full write access to the folder, the --verbose --help command used to extract datadir will write an index file to it, causing the following initialize step to fail because there are files in datadir.

To reproduce:
...
docker run -e MYSQL_ROOT_PASSWORD=rot -v /tmp/data:/var/lib/mysql mysql:latest --log-bin=somename --server-id=1
...
where /tmp/data is writeable.

A possible workaround is to add --log-bin-index=/tmp/junk.index to the --verbose --help command.
This is a bug in the server, similar to #69

@ltangvald
Copy link
Collaborator Author

Related bugs.mysql.com issue: http://bugs.mysql.com/bug.php?id=78957

@ndelitski
Copy link

+1

@tianon
Copy link
Member

tianon commented Jan 22, 2016

This has been fixed now, right? 😄

@ltangvald
Copy link
Collaborator Author

Yeah, this bug was fixed in 5.7.10 (only affected 5.7.9)

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

No branches or pull requests

3 participants