MySQL Bugs: #81294: mysql-docker immediately stops after running

Bug #81294	mysql-docker immediately stops after running
Submitted:	3 May 2016 13:25	Modified:	8 Aug 2016 11:44
Reporter:	Zeke D	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Package Repos	Severity:	S1 (Critical)
Version:	5.6	OS:	Any (Docker)
Assigned to:	Lars Tangvald	CPU Architecture:	Any
Tags:	5.6, mysql-docker

Description:
Hi,

Docker mysql keeps crashing for me, not sure what is going on as the containers are clean and I wipe all dockers volumes as well as part of my development process

```
db_1        | Running mysql_install_db
db_1        | 2016-04-28 19:25:32 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
db_1        | 2016-04-28 19:25:32 0 [Note] /usr/sbin/mysqld (mysqld 5.6.30) starting as process 12 
dockermagic_db_1 exited with code 141
```

To Solve this issue i have to destroy and recreate the docker machine, it is the only way to move past this error...

The github link is here: https://github.com/mysql/mysql-docker

I also reported a bug with docker official mysql image: https://github.com/docker-library/mysql/issues/3

This is development stopper so any advice would be highly appreciated

How to repeat:
simply use mysql-docker in a docker-machine with plenty of other services running

Suggested fix:
If a command like this would work completely I would be satisfied, however, it does not entirely solve the problem

docker volume rm $(docker volume ls -qf dangling=true)

Hi

Are you running a custom Docker image? Based on the error message the entrypoint script is from before October 22, but the server version is 5.6.30 which wasn't available then.

If so could you post the entrypoint script and Dockerfile used?

Sorry, ignore the above comment, I thought you were using the official image.

How are you starting the image?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".