Differences from the official
This image can create arbitrary amount of databases on startup.
Supported tags and respective
What is MariaDB?
MariaDB is a community-developed fork of the MySQL relational database management system intended to remain free under the GNU GPL. Being a fork of a leading open source software system, it is notable for being led by the original developers of MySQL, who forked it due to concerns over its acquisition by Oracle. Contributors are required to share their copyright with the MariaDB Foundation.
The intent is also to maintain high compatibility with MySQL, ensuring a "drop-in" replacement capability with library binary equivalency and exact matching with MySQL APIs and commands. It includes the XtraDB storage engine for replacing InnoDB, as well as a new storage engine, Aria, that intends to be both a transactional and non-transactional engine perhaps even included in future versions of MySQL.
How to use this image
mariadb server instance
docker run --name some-mariadb -e MYSQL_ROOT_PASSWORD=mysecretpassword -d mariadb
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-mariadb:mysql -d application-that-uses-mysql
... or via
docker run -it --link some-mariadb:mysql --rm mariadb 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_DATABASES 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 a list of names of databases 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. The list is space separated, so keep that in mind when deciding on database names.
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.7.1.
Support for older versions (down to 1.0) is provided on a best-effort basis.
Documentation for this image is stored in the
mariadb/ directory of the
docker-library/docs GitHub repo. Be sure to familiarize yourself with the repository's
README.md file before attempting a pull request.
If you have any problems with or questions about this image, please contact us through a GitHub issue.
You can also reach many of the official image maintainers via the
#docker-library IRC channel on Freenode.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.