MY-010123 error running version 8.0

[ldesousa]

I would like to create an image from the Dockerfile for version 8.0. I have checked out the contents of the 8.0 folder and the docker build command concludes successfully. However, when I run the image it exits immediately. In the logs I have the following:

$ docker logs mysql
2018-08-16T14:15:18.725201Z 0 [Warning] [MY-011070] [Server] 'Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it' is deprecated and will be removed in a future release.
2018-08-16T14:15:18.725320Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.12) starting as process 1
2018-08-16T14:15:18.728605Z 0 [ERROR] [MY-010123] [Server] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!
2018-08-16T14:15:18.728633Z 0 [ERROR] [MY-010119] [Server] Aborting
2018-08-16T14:15:18.729717Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.12)  MySQL Community Server - GPL.

I understand that mySQL is not supposed to be run in a root session, is that the issue? What can I do to avoid this error?

Thank you.

[tianon]

I have checked out the contents of the 8.0 folder and the docker build command concludes successfully.

From the error message, it would appear you've made at least some changes.

The stock ENTRYPOINT script we provide steps down from root almost immediately:

mysql/8.0/docker-entrypoint.sh

Line 91 in b39f1e5

exec gosu mysql "$BASH_SOURCE" "$@"

See https://dev.mysql.com/doc/refman/8.0/en/server-options.html#option_mysqld_user for more details from upstream.

Any particular reason you're building your own custom image?

[ldesousa]

I would like to restore a dump in the Dockerfile itself, that is why I am editing the it. However, I get the error reported above without changes to the original Dockerfile.

[tianon]

I can't reproduce a failure to run, so I think we'll need more details:

$ docker pull mysql:8.0
8.0: Pulling from library/mysql
Digest: sha256:d39a8ab7679df309e7eff6ddba434ad5747cc2a2acee2d7c60d8221c9acedcad
Status: Image is up to date for mysql:8.0

$ docker run -d --name test -e MYSQL_ROOT_PASSWORD=foobar mysql:8.0
d81c33567ff972f836477fc77d1d9747a9cb39a73e1c80e670d146689a884ecd

$ docker logs --tail=1 test
2018-08-20T22:31:28.758699Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.12'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server - GPL.

As for creating an image with "pre-baked" contents, you should be able to do so FROM mysql:8.0 (without copying the Dockerfile) by modifying --datadir (either via command-line or file-based configuration of mysqld). There's more discussion on that point over in #255.

[wglambert]

Closing as issue seems resolved and there isn't an issue with the image that we could alleviate

If you have further questions you could ask the Docker Community Forums, the Docker Community Slack, or Stack Overflow. As these repositories are for issues with the image and not necessarily for questions of usability