Revision as of 09:33, 3 July 2023

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.

This is the general documentation for normal and common general usage, for professional usage please use Production DataBases : mysql that is the same as MariaDB but with several modifications focused on production and security!

Installation

The Alpine Linux repositories no longer include the actual MySQL binaries, installing the mysql-* packages will instead install MariaDB.

Installing mariadb will create the user mysql. When the database is initialized, two users will be added to the database: root and mysql. By default these users will only be accessible if you are logged in as the corresponding system user.

apk add mysql mysql-client

Installing the above packages will add the main components of MariaDB to the system: mariadb-cient and mariadb-server. Other available packages are described in the table below, and are listed in order of relevance for a production server.

MySQL name package	Since Alpine:	Brief usage	Related package
mysql	v2	a transitional package that installs mariadb	mariadb
mysql-client	v2	a transitional package that installs the mariadb client tools	mariadb-client
mariadb	v2	server equivalent to mysql-server	mariadb-common
mariadb-client	v2	connection command line and tools	mariadb-common
mariadb-doc	v3.0	manpages for mariadb	man man-pages
mariadb-connector-odbc	edge	coding or making OS level connections, to any DB without libs install	.
mariadb-connector-c	v3.8	coding connection on C sources	mariadb-connector-c-dev
mariadb-backup	v3.8	tool for physical online backups, no longer widely used	.
mariadb-server-utils	v3.8	server commands not widely used, in past was inside MariaDB package	.
mariadb-dev	v3.1	development files for MariaDB	.
mariadb-test	v3.3	testing suite from MariaDB tools	.
mariadb-mytop	v3.9	data performance monitoring	.
mariadb-plugin-rocksdb	v3.9	plain key-value event relational for data	.
mariadb-static	v3.8	static libs for static non depends linking in builds	.
mariadb-embedded	v3.9	the libmysqld identical interface as the C client	mariadb-embedded-dev
mariadb-embedded-dev	v3.9	use the normal mysql.h and link with libmysqld instead of libmysqlclient	mariadb-dev
mariadb-openrc	v3.8	separate scripts, in past was embebed on server package	.

Initialization

The version of MariaDB in the Alpine repositories behave like the MySQL tarball. No graphical tools are included.

The datadir located at /var/lib/mysql must be owned by the mysql user and group. The location of the datadir can be changed by editing the mariadb service file in /etc/init.d. The new location will also need to be set by adding datadir=<YOUR_DATADIR> in the [mysqld] section in a mariadb configuration file.

Normal initialization of mariadb can be done as follows:

Initialize the main mysql database, and the data dir as standardized to /var/lib/mysql by running /etc/init.d/mariadb setup
Start the main service. At this point there will be no root password set. /etc/init.d/mariadb start
Secure the database by running mysql_secure_installation
Setup permissions for managing others users and databases

Configuration

In order to help with the basic configuration of the database engine, MariaDB provides mysql_secure_installation. This script walks you through the basics of securing the database. The options are explained below.

Enter current password for root (enter for none): If you have previously set up a root password, provide it here and press enter. If not, just press enter.
Switch to unix_socket authentication [Y/n] Setting the root password or using the Unix_socket ensures that only admins can log into engine database. For non-production servers just press "n" to setup a root password, which will give you the response ... skipping.
Change the root password? [Y/n] Here you can change the root password, or set one if needed. Press "Y" and enter the new password.
Remove anonymous users? [Y/n] Remove anonymous users created to log in using socket authentication. Unless you're sure you need this, answer "Y" to remove them.
Disallow root login remotely? [Y/n] Normally, root should only be allowed to connect from 'localhost' in order to protect from password sniffing attempts over the network. Answer "Y".
Remove test database and access to it? [Y/n] By default, MariaDB comes with a database named 'test' that anyone can access. If this is not needed, answer "Y".
Reload privilege tables now? [Y/n] Reloading the privilege tables will ensure that all changes made so far will take effect immediately. Answer "Y".

After the script exits, restart the service with rc-service mariadb restart

To start the database daemon on every boot, run rc-update add mariadb default

Configuration files and customization

Rather than being stored in my.cnf, configuration settings for MariaDB are now organized in separate files. The primary configuration is done by adding files to /etc/my.cnf.d/. User-specific configuration files are stored in ~/.my.cnf. User-specific configuration files are loaded after the system-wide configuration. The locations of the various configuration files are listed below.

Config file	Path and name	Versions of Alpine	Contents to configure
my.cnf	/etc/mysql/my.cnf	v2 to v3.8	All the directives, global config file
mariadb-server.cnf	/etc/my.cnf.d/mariadb-server.cnf	since 3.9	First global config file, main directives
.my.cnf	$HOME	all	user name only config directives

As previously mentioned, this page describes basic usage of MariaDB. For professional usage, Production DataBases : mysql should also be referenced.

The following command will configure the server to accept all incoming connections. This should only be done for development, or if the database is not exposed to the Internet or a sensitive network.

For simple installations, disabling hostname search can improve performance, but is only useful for local servers.

Updating or coming from upgrading

When upgrading between Alpine Linux releases, MariaDB may also have a major version change, and the databases should be upgraded to match. The recommended steps in this process are detailed below.

While it may no longer be strictly necessary, it's useful to backup your databases before upgrading the database version.
Update Alpine Linux and the MariaDB/MySQL packages.
Run mysql_upgrade -u root -p script, and provide the password for the root database user.
Restart the service by running rc-service mariadb restart.

If mysql_upgrade fails because MySQL cannot start, try running MySQL in safemode with mysqld_safe --datadir=/var/lib/mysql/, and then run mysql_upgrade -u root -p again.

@@ Line 9: / Line 9: @@
 Installing <code>mariadb</code> will create the user <code>mysql</code>. When the database is initialized, two users will be added to the database: <code>root</code> and <code>mysql</code>. By default these users will only be accessible if you are logged in as the corresponding system user.
-<pre><nowiki>
+{{Cmd|apk add mysql mysql-client}}
-apk add mysql mysql-client
-</nowiki></pre>
 Installing the above packages will add the main components of MariaDB to the system: <code>mariadb-cient</code> and <code>mariadb-server</code>. Other available packages are described in the table below, and are listed in order of relevance for a production server.
@@ Line 58: / Line 56: @@
 The version of MariaDB in the Alpine repositories behave like the MySQL tarball. No graphical tools are included.
-The ''datadir'' located at <code>/var/lib/mysql</code> must be owned by the mysql user and group. The location of the ''datadir'' can be changed by editing the <code>mariadb</code> service file in <code>/etc/init.d</code>. The new location will also need to be set by adding <code><nowiki>datadir=<YOUR_DATADIR></nowiki></code> in the <code>[mysqld]</code> section in a mariadb configuration file.
+The ''datadir'' located at {{Path|/var/lib/mysql}} must be owned by the mysql user and group. The location of the ''datadir'' can be changed by editing the <code>mariadb</code> service file in {{Path|/etc/init.d}}. The new location will also need to be set by adding <code><nowiki>datadir=<YOUR_DATADIR></nowiki></code> in the <code>[mysqld]</code> section in a mariadb configuration file.
 Normal initialization of mariadb can be done as follows:
-# Initialize the main mysql database, and the data dir as standardized to <code>/var/lib/mysql</code> by running <code>/etc/init.d/mariadb setup</code>
+# Initialize the main mysql database, and the data dir as standardized to {{Path|/var/lib/mysql}} by running <code>/etc/init.d/mariadb setup</code>
 # Start the main service. At this point there will be no root password set. <code>/etc/init.d/mariadb start</code>
 # Secure the database by running <code>mysql_secure_installation</code>
@@ Line 86: / Line 84: @@
 === Configuration files and customization ===
-Rather than being stored in <code>my.cnf</code>, configuration settings for MariaDB are now organized in separate files. The primary configuration is done by adding files to <code>/etc/my.cnf.d/</code>. User-specific configuration files are stored in <code>~/.my.cnf</code>. User-specific configuration files are loaded after the system-wide configuration. The locations of the various configuration files are listed below.
+Rather than being stored in {{Path|my.cnf}}, configuration settings for MariaDB are now organized in separate files. The primary configuration is done by adding files to {{Path|/etc/my.cnf.d/}}. User-specific configuration files are stored in {{Path|~/.my.cnf}}. User-specific configuration files are loaded after the system-wide configuration. The locations of the various configuration files are listed below.
 {| class="wikitable"
@@ Line 92: / Line 90: @@
 ! Config file !! Path and name !! Versions of Alpine !! Contents to configure
 |-
-| my.cnf || <nowiki>/etc/mysql/my.cnf</nowiki> || v2 to v3.8 || All the directives, global config file
+| my.cnf || {{Path|/etc/mysql/my.cnf}} || v2 to v3.8 || All the directives, global config file
 |-
-| mariadb-server.cnf || /etc/my.cnf.d/mariadb-server.cnf || since 3.9 || First global config file, main directives
+| mariadb-server.cnf || {{Path|/etc/my.cnf.d/mariadb-server.cnf}} || since 3.9 || First global config file, main directives
 |-
 | .my.cnf || <nowiki>$HOME</nowiki> || all || user name only config directives
@@ Line 103: / Line 101: @@
 * The following command will configure the server to accept all incoming connections. This should only be done for development, or if the database is not exposed to the Internet or a sensitive network.
-<pre>
+{{Cmd|<nowiki>
-<nowiki>
 sed -i "s|.*bind-address\s*=.*|bind-address=0.0.0.0|g" /etc/mysql/my.cnf
 sed -i "s|.*bind-address\s*=.*|bind-address=0.0.0.0|g" /etc/my.cnf.d/mariadb-server.cnf
 </nowiki>
-</pre>
+}}
 * For simple installations, disabling hostname search can improve performance, but is only useful for local servers.
-<pre>
+{{Cmd|<nowiki>
-<nowiki>
 sed -i "s|.*skip-networking.*|skip-networking|g" /etc/mysql/my.cnf
 sed -i "s|.*skip-networking.*|skip-networking|g" /etc/my.cnf.d/mariadb-server.cnf
 </nowiki>
-</pre>
+}}
 == Updating or coming from upgrading ==

MariaDB: Difference between revisions