Shulou(Shulou.com)05/31 Report--

This article mainly shows you "what will happen when you use docker/mysql under Macosx", the content is simple and clear, and I hope it can help you solve your doubts. Let me lead you to study and learn "what will happen when you use docker/mysql under Macosx".

Problem description

If you specify a local directory to replace / var/lib/mysql under macosx, an error in file permissions will occur at run time, causing mysqld to fail to run properly

Creating mysql_test-mysql_1Attaching to mysql_test-mysql_1test-mysql_1 | Initializing databasetest-mysql_1 | 2016-03-23T04:32:37.437789Z 0 [Warning] Setting lower_case_table_names=2 because file system for / var/lib/mysql/ is case insensitivetest-mysql_1 | 2016-03-23T04:32:37.466955Z 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.test-mysql_1 | 2016-03-23T04:32:37.467828Z 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.test-mysql_1 | 2016-03-23T04:32:37.468824Z 0 [ERROR] InnoDB: Operating system error number 13 in afile operation.test-mysql_1 | 2016-03-23T04:32:37.468912Z 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.test-mysql_1 | 2016-03-23T04:32:37.470280Z 0 [ERROR] InnoDB: Cannot open datafile'. / ibdata1'test-mysql_1 | 2016-03-23T04:32:37.470309Z 0 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data testing MySQL 1 | 2016-03-23T04:32:37.470317Z 0 [ERROR] InnoDB: InnoDB Database creation was aborted with error Cannot open a file. You may need to delete the ibdata1 file before trying to start up again.test-mysql_1 | 2016-03-23T04:32:38.073222Z 0 [ERROR] Plugin 'InnoDB' init function returned error.test-mysql_1 | 2016-03-23T04:32:38.073268Z 0 [ERROR] Plugin' InnoDB' registration as a STORAGE ENGINE failed.test-mysql_1 | 2016-03-23T04:32:38.073283Z 0 [ERROR] Failed to initialize plugins.test-mysql_1 | 2016-03-23T04:32:38.073289Z 0 [ERROR] Abortingtest-mysql_1 | mysql_test-mysql_1 exited with code 1

Solution

Create a mysqld startup script under the scripts directory

#! / bin/bash# From https://github.com/docker-library/mysql/issues/99set-e # fail on any errorecho'* Working around permission errors in Docker on Mac locally by making sure that "mysql" uses the same uid and gid as the host volume'TARGET_UID=$ (stat-c "% u" / var/lib/mysql) echo'- Setting mysql user to use uid'$TARGET_UIDusermod-o-u $TARGET_UID mysql | | trueTARGET_GID=$ (stat-c "% g" / var/lib/) Mysql) echo'- Setting mysql group to use gid'$TARGET_GIDgroupmod-o-g $TARGET_GID mysql | | trueechoecho'* Starting MySQL'chown-R mysql:root / var/run/mysqld//entrypoint.sh mysqld-- user=mysql-- console

Create a docker-compose.py and specify the run-mysqld.sh script as the container entry

Test-mysql: image: mysql ports:-"3306 mysql ports" volumes:-/ localhost/mysql/data:/var/lib/mysql -. / scripts/run-mysqld.sh:/run-mysqld.sh environment:-MYSQL_DATABASE=play-MYSQL_USER=play-MYSQL_PASSWORD=play-MYSQL_ROOT_PASSWORD=123456 entrypoint: / run-mysqld.sh

Run the docker-compose up command to start the container

The above is all the contents of this article entitled "what are the problems in using docker/mysql under Macosx?" Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.