Cannot run mysql:5.7.28 with '-t' option

[m15o]

Cannot run mysql:5.7.28 with '-t' option:
docker run --rm -t -e MYSQL_ALLOW_EMPTY_PASSWORD=true mysql:5.7.28

2019-10-16 06:25:00+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.28-1debian9 started.
2019-10-16 06:25:00+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2019-10-16 06:25:00+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.28-1debian9 started.
2019-10-16 06:25:00+00:00 [Note] [Entrypoint]: Initializing database files
2019-10-16T06:25:00.882890Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-10-16T06:25:01.081984Z 0 [Warning] InnoDB: New log files created, LSN=45790
2019-10-16T06:25:01.122587Z 0 [Warning] InnoDB: Creating foreign key constraint system tables.
2019-10-16T06:25:01.182468Z 0 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: aed9b346-efdd-11e9-bac1-0242ac110004.
2019-10-16T06:25:01.186354Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2019-10-16T06:25:01.922428Z 0 [Warning] CA certificate ca.pem is self signed.
2019-10-16T06:25:02.027645Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
2019-10-16 06:25:04+00:00 [Note] [Entrypoint]: Database files initialized
2019-10-16 06:25:04+00:00 [Note] [Entrypoint]: Starting temporary server
Please enable --log-error option or set appropriate redirections for standard output and/or standard error in daemon mode.
2019-10-16 06:25:04+00:00 [ERROR] [Entrypoint]: Unable to start server.

mysql:5.7.27 has no problem with '-t' option:
docker run --rm -t -e MYSQL_ALLOW_EMPTY_PASSWORD=true mysql:5.7.27

[m15o]

Cannot run on circleci either:

2019-10-16 04:35:18+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.28-1debian9 started.
2019-10-16 04:35:18+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2019-10-16 04:35:18+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.28-1debian9 started.
2019-10-16 04:35:18+00:00 [Note] [Entrypoint]: Initializing database files
2019-10-16T04:35:18.322128Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-10-16T04:35:18.488295Z 0 [Warning] InnoDB: New log files created, LSN=45790
2019-10-16T04:35:18.517011Z 0 [Warning] InnoDB: Creating foreign key constraint system tables.
2019-10-16T04:35:18.572621Z 0 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 5b4f2653-efce-11e9-9e26-0242c0a8e003.
2019-10-16T04:35:18.572869Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2019-10-16T04:35:19.184439Z 0 [Warning] CA certificate ca.pem is self signed.
2019-10-16T04:35:19.317383Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
2019-10-16 04:35:21+00:00 [Note] [Entrypoint]: Database files initialized
2019-10-16 04:35:21+00:00 [Note] [Entrypoint]: Starting temporary server
Please enable --log-error option or set appropriate redirections for standard output and/or standard error in daemon mode.
2019-10-16 04:35:21+00:00 [ERROR] [Entrypoint]: Unable to start server.

Exited with code 1

[ruudk]

Thanks for posting this as I just discovered the same issue on our CircleCI. It picked up 5.7.28 overnight.

[ruudk]

I'm unable to reproduce this on macOS with the same MySQL version. I find this interesting:

Please enable --log-error option or set appropriate redirections for standard output and/or standard error in daemon mode.

Could it be that CircleCI runs the container in a different way?

[m15o]

I am also running docker on macOS.

It runs perfectly without '-t' or '--tty' option like this:
docker run --rm -e MYSQL_ALLOW_EMPTY_PASSWORD=true mysql:5.7.28

But it dont with '-t' option:
docker run --rm -t -e MYSQL_ALLOW_EMPTY_PASSWORD=true mysql:5.7.28

[tgandrews]

I get the same issue on Windows. It is not just Linux

[raptor235]

Same issue here... all our builds started failing this morning.

[DannyvdSluijs]

Same issue here. Sadly no additional information on the why. Setting the mysql image from 5.7 to 5.7.27 makes the builds work again.

[FelicianoTech]

I can confirm that this is affecting many CircleCI customers using the 5.7 tag.

For CircleCI users seeing this, temp workaround listed here.

[ltangvald]

The 5.7.28 image is the first built from a fairly big refactoring effort done, so might be related to that. Will look into this.

[tianon]

@ltangvald I've confirmed it's related to the new use of --daemonize -- the old script on 5.7 didn't use --daemonize 😞

Do we need to set --log-error explicitly to /dev/stderr or something?

[ltangvald]

Yup, just found the same thing :) Yeah, I think that should work.

[ltangvald]

That should work for 8.0 too (just isn't required), so don't think we need to add any extra version checks.

[tianon]

Hopefully you've got a better handle on how to make that work because my testing is coming up empty. 😅

Doing --log-error=/dev/stderr adds .err on the end, and explicitly creating a symlink with an existing extension to avoid that added suffix leads to things like Could not open file '/var/log/mysql/error.log' for error logging: Permission denied. 😕

[ltangvald]

I'll give it a try. If not, we could fall back to the 5.6-way of doing it for 5.7 as well, just to get this fixed quickly, i.e. change the test to only 8.0 using daemonize for the temporary startup.

[ltangvald]

Yeah, I couldn't find a quick fix for it, so I made pr #601 to revert to the 5.6 way for now