MariaDB is a community-developed fork of the MySQL relational database management system intended to remain free under the GNU GPL. It is notable for being led by the original developers of MySQL, who forked it due to concerns over its acquisition by Oracle. MariaDB intends 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.
- Based on the super slim tklx/base (Debian GNU/Linux).
- MariaDB installed from Debian.
- Uses tini for zombie reaping and signal forwarding.
- Includes
USER mysql
to restrict the privileges of mysqld. - Includes
VOLUME /var/lib/mysql
for database persistence. - Includes
EXPOSE 3306
, so standard container linking will make it automatically available to the linked containers.
Note: If there is no database initialized when the container starts, then a default database will be created. The container will not accept incoming connections until initialization completes. This may cause issues when using automation tools such as docker-compose
, which start several containers simultaneously.
$ docker run --name some-mariadb -e MYSQL_ROOT_PASSWORD=my-secret-pw -d tklx/mariadb
$ docker run --name some-app --link some-mariadb:mysql -d application-that-uses-mysql
$ chown -R 999:999 /my/own/datadir
$ docker run --name some-mariadb -v /my/own/datadir:/var/lib/mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d tklx/mariadb
$ docker run -it --link some-mariadb:mysql --rm tklx/mariadb sh -c 'exec mysql -h"$MYSQL_PORT_3306_TCP_ADDR" -P"$MYSQL_PORT_3306_TCP_PORT" -uroot -p"$MYSQL_ENV_MYSQL_ROOT_PASSWORD"'
More information about the MySQL command line client can be found in the MySQL documentation
$ docker run --name some-mariadb -v /my/custom/conf.d/path:/etc/mysql/conf.d -e MYSQL_ROOT_PASSWORD=my-secret-pw -d tklx/mariadb
Note that users on host systems with SELinux enabled may see issues with this. The current workaround is to assign the relevant SELinux policy type to the new config file so that the container will be allowed to mount it:
$ chcon -Rt svirt_sandbox_file_t /my/custom/conf.d/path
$ docker exec some-mariadb sh -c 'exec mysqldump --all-databases -uroot -p"$MYSQL_ROOT_PASSWORD"' > /some/path/on/your/host/all-databases.sql
Note: any pre-existing database in the datadir will always be left untouched on container startup.
This variable is mandatory and specifies the password that will be set for the MariaDB root
superuser account.
This variable is optional and allows to specify the name of a database to be created on image startup. If a user/password was supplied (see below) then that user will be granted superuser access (corresponding to GRANT ALL
) to this database.
These variables are optional, used in conjunction to create a new user and to set that user's password. This user will be granted superuser permissions for the database specified by the MYSQL_DATABASE
variable. Both variables are required for a user to be created.
This is an optional variable. Set to yes
to allow the container to be started with a blank password for the root user. NOTE: Setting this variable to yes
is not recommended unless you really know what you are doing, since this will leave your MariaDB instance completely unprotected, allowing anyone to gain complete superuser access.
Sets the root (not the user specified in MYSQL_USER
!) user as expired once init is complete, forcing a password change on first login.
# interactive root shell
$ docker run --rm -it -u root tklx/mongodb /bin/bash
# server options
$ docker run -it --rm tklx/mariadb --verbose --help
# client options
$ docker run -it --rm tklx/mariadb mysql --verbose --help
The Docker image is built, tested and pushed by CircleCI from source hosted on GitHub.
- Tag:
x.y.z
refers to a release (recommended). - Tag:
latest
refers to the master branch.
Currently on major version zero (0.y.z). Per Semantic Versioning, major version zero is for initial development, and should not be considered stable. Anything may change at any time.
TKLX uses a central issue tracker on GitHub for reporting and tracking of bugs, issues and feature requests.