This image of tokudb is builded from official mariadb docker image.
How to use this image
tokudb server instance
docker run --name some-tokudb -e MYSQL_ROOT_PASSWORD=mysecretpassword -d goldy/tokudb
This image includes
EXPOSE 3306 (the standard MySQL port), so container linking will make it automatically available to the linked containers (as the following examples illustrate).
connect to it from an application
Since MariaDB is intended as a drop-in replacement for MySQL, it can be used with many applications.
docker run --name some-app --link some-tokudb:mysql -d application-that-uses-mysql
... or via
docker run -it --link some-tokudb:mysql --rm goldy/tokudb sh -c 'exec mysql -h"$MYSQL_PORT_3306_TCP_ADDR" -P"$MYSQL_PORT_3306_TCP_PORT" -uroot -p"$MYSQL_ENV_MYSQL_ROOT_PASSWORD"'
mariadb image uses several environment variables which are easy to miss. While not all the variables are required, they may significantly aid you in using the image.
The variable names are prefixed with
MYSQL_ since the binary is
mysqld, and since the intention is to be a drop-in replacement for MySQL, as mentioned above.
This is the one environment variable that is required. This environment variable should be what you want to set the password for the
root user to be. In the above example, it is being set to "
These optional environment variables are used in conjunction to both create a new user and set that user's password, which will subsequently be granted all permissions for the database specified by the optional
MYSQL_DATABASE variable. Note that if you only have one of these two environment variables, then neither will do anything -- these two are required to be used in conjunction with one another.
Additionally, there is no need to specify
root, as the
root user already exists by default, and the password of that user is controlled by
MYSQL_ROOT_PASSWORD (see above).
This optional environment variable denotes the name of a database to create. If a user/password was supplied (via the
MYSQL_PASSWORD environment variables) then that user will be granted (via
GRANT ALL) access to this database.
If there is no database initialized when the container starts, then a default database will be created. While this is the expected behavior, this means that it will not accept incoming connections until such initialization completes. This may cause issues when using automation tools, such as
docker-compose, which start several containers simultaneously.
Supported Docker versions
This image is officially supported on Docker version 1.6.2.
Support for older versions (down to 1.0) is provided on a best-effort basis.