springhgui/alisql repository overview

⁠Supported tags and respective Dockerfile links

• 5.6.32-7, 5.6.32, 5.6, latest (Debian based Dockerfile⁠)
• 5.6.32-7-centos, 5.6.32-centos, 5.6-centos, centos(CentOS based Dcokerfile⁠)

⁠Quick reference

• Where to file issues: https://github.com/fungo/AliSQL-docker/issues⁠
• AliSQL official wiki: https://github.com/alibaba/AliSQL/wiki⁠

⁠What is AliSQL?

AliSQL is a MySQL branch originated from Alibaba Group. It is based on the MySQL official release and has many feature and performance enhancements. AliSQL has proven to be very stable and efficient in production environment. It can be used as a free, fully compatible, enhanced and open source drop-in replacement for MySQL.

AliSQL has been an open source project since August 2016. It is being actively developed by engineers from Alibaba Group. Moreover, it includes patches from Percona, WebScaleSQL, and MariaDB. AliSQL is a fruit of community effort. Everyone is welcomed to get involved.

For more information, please visit https://github.com/alibaba/AliSQL⁠.

⁠How to use this image

Because AliSQL has TokuDB storage engine statically built-in, and Transparent Huge Pages(THP) will prohibit TokuDB from starting (Why TokuDB hates Transparent HugePages⁠) , THP must be disabled(echo never > sys/kernel/mm/transparent_hugepage/enabled).

All the usages of official mysql image⁠ are supported by AliSQL, below are just some notable examples:

⁠Start a alisql server instance

Starting a AliSQL instance is simple:

$ docker run --name some-alisql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d alisql/alisql:tag

⁠Container shell access and viewing AliSQL logs

The docker exec command allows you to run commands inside a Docker container. The following command line will give you a bash shell inside your alisql container:

$ docker exec -it some-alisql bash

The AliSQL Server log is available through Docker's container log:

$ docker logs some-alisql

⁠Using a custom MySQL configuration file

The MySQL startup configuration is specified in the file /etc/mysql/my.cnf, and that file in turn includes any files found in the /etc/mysql/conf.d directory that end with .cnf. Settings in files in this directory will augment and/or override settings in /etc/mysql/my.cnf. If you want to use a customized MySQL configuration, you can create your alternative configuration file in a directory on the host machine and then mount that directory location as /etc/mysql/conf.d inside the alisql container.

If /my/custom/config-file.cnf is the path and name of your custom configuration file, you can start your alisql container like this (note that only the directory path of the custom config file is used in this command):

$ docker run --name some-alisql -v /my/custom:/etc/mysql/conf.d -e MYSQL_ROOT_PASSWORD=my-secret-pw -d alisql/alisql:tag

This will start a new container some-alisql where the MySQL instance uses the combined startup settings from /etc/mysql/my.cnf and /etc/mysql/conf.d/config-file.cnf, with settings from the latter taking precedence.

⁠Environment Variables

• MYSQL_ROOT_PASSWORD
• MYSQL_DATABASE
• MYSQL_USER, MYSQL_PASSWORD
• MYSQL_ALLOW_EMPTY_PASSWORD
• MYSQL_RANDOM_ROOT_PASSWORD
• MYSQL_ONETIME_PASSWORD