The MariaDB project signs their MariaDB packages for Debian, Ubuntu, Fedora, and Red Hat. This page documents information about the keys that we use and have used.

MariaDB Community Server Debian / Ubuntu key

Our MariaDB Community Server repositories for Debian "Sid" and the Ubuntu 16.04 and beyond "Xenial" use the following GPG signing key. As detailed in MDEV-9781, APT 1.2.7 (and later) prefers SHA2 GPG keys and now prints warnings when a repository is signed using a SHA1 key like our previous GPG key. We have created a SHA2 key for use with these.

Information about this key:

• The short Key ID is: 0xC74CD1D8

• The long Key ID is: 0xF1656F24C74CD1D8

• The full fingerprint of the key is: 177F 4010 FE56 CA33 3630 0305 F165 6F24 C74C D1D8

• The key can be added on Debian-based systems using the following command:

• Usage of the apt-key command is deprecated in the latest versions of Debian and Ubuntu, and the replacement method is to download the keyring file to the /etc/apt/trusted.gpg.d/ directory. This can be done with the following:

MariaDB Community Server RPM / Source Keys

MariaDB Enterprise GPG Keys

MariaDB MaxScale GPG Keys

Configuring Repositories

See the page for details on using the mariadb_repo_setup and mariadb_es_repo_setup scripts to configure repositories that use these keys.

See the on configuring MariaDB Foundation repositories that use these keys.

_{This page is licensed: CC BY-SA / Gnu FDL}

MariaDB Server does not currently provide a .pkg installer for macOS. For information about how to install MariaDB Server on macOS using Homebrew, see .

_{This page is licensed: CC BY-SA / Gnu FDL}

The following article is about different issues people have encountered when installing MariaDB on RHEL / CentOS.

It is highly recommended to where possible.

In RHEL/ CentOS it is also possible to install a or a . The RPM is the preferred version, except if you want to install many versions of MariaDB or install MariaDB in a non standard location.

Replacing MySQL

If you removed an MySQL RPM to install MariaDB, note that the MySQL RPM on uninstall renames /etc/my.cnf

MariaDB source RPMs (SRPMs) are not packaged on all platforms for which MariaDB RPMs are packaged.

The reason is that MariaDB's build process relies heavily on for a lot of things. In this specific case, MariaDB's build process relies on to build RPMs. The specific package generator that it uses to build RPMs is called .

Support for source RPMs in became usable with MariaDB's build system starting from around . This means that we do not produce source RPMs on platforms where the installed version is older than that.

See also .

_{This page is licensed: CC BY-SA / Gnu FDL}

Users need to run , without parameters to create a data directory, e.g

Then you can start server like this

If you like to customize the server instance (data directory, install as service etc), please refer to

_{This page is licensed: CC BY-SA / Gnu FDL}

This article describes how to download the RPM files and install them using therpm command.

It is highly recommended to Install MariaDB with yum where possible.

Navigate toand choose the desired database version and then select the RPMs that match your Linux distribution and architecture.

Clicking those links takes you to a local mirror. Choose the rpms link and download the desired packages. The packages will be similar to the following:

MariaDB-client-5.2.5-99.el5.x86_64.rpm
MariaDB-debuginfo-5.2.5-99.el5.x86_64.rpm
MariaDB-devel-5.2.5-99.el5.x86_64.rpm
MariaDB-server-5.2.5-99.el5.x86_64.rpm
MariaDB-shared-5.2.5-99.el5.x86_64.rpm
MariaDB-test-5.2.5-99.el5.x86_64.rpm

For a standard server installation you will need to download at least the client, shared, and server RPM files. See About the MariaDB RPM Files for more information about what is included in each RPM package.

After downloading the MariaDB RPM files, you might want to check their signatures. See Checking MariaDB RPM Package Signatures for more information about checking signatures.

Prior to installing MariaDB, be aware that it will conflict with an existing installation of MySQL. To check whether MySQL is already installed, issue the command:

If necessary, you can remove found MySQL packages before installing MariaDB.

To install MariaDB, use the command:

You should see output such as the following:

Be sure to follow the instructions given in the preceding output and create a password for the root user either by using or by running the /usr/bin/mysql_secure_installation script.

Installing the MariaDB RPM files installs the MySQL tools in the /usr/bin directory. You can confirm that MariaDB has been installed by using the client program. Issuing the command mariadb should give you the MariaDB cursor.

See Also

_{This page is licensed: CC BY-SA / Gnu FDL}

MariaDB Corporation provides package tarballs for some MariaDB database products.

Package tarballs provide multiple benefits:

• Package tarballs are compressed tar archives that contain software packages.

• Software packages can be installed using the operating system's package manager without relying on a remote repository.

• RPM (.rpm) files are distributed for CentOS, Red Hat Enterprise Linux (RHEL), and SUSE Linux Enterprise Server (SLES).

• DEB (.deb) files are distributed for Debian and Ubuntu.

If you want to deploy MariaDB database products without using a package tarball, are available. Available deployment methods are component-specific.

Use Cases

MariaDB database products can be deployed with package tarballs to support use cases, such as:

• Transfer the package tarball to an air-gapped network for installation without an internet connection

• Install software using a package manager without configuring a package repository

• Automatically install missing dependencies using a package manager

Compatibility

The following MariaDB database products can be deployed using package tarballs:

• MariaDB Community Server 10.5

• MariaDB Community Server 10.6

• MariaDB Enterprise Server 10.5

• MariaDB Enterprise Server 10.6

Download a Package Tarball

MariaDB Corporation provides package tarballs (.debs.tar, .rpms.tar) to support customers who leverage in-house package repositories to distribute software to their servers. Secure any such repository to prevent outside access.

MariaDB Corporation provides multiple interfaces to download package tarballs.

Installation From Package Tarball

Once downloaded and extracted, you can:

• Install .rpm packages (RHEL, CentOS, and SLES): rpm -i

• Install .deb packages (Debian, Ubuntu): dpkg -i

• Install from the simple package repositories included in the tarball. Missing dependencies will be resolved when using the apt, yum, or zypper

Installation loads software to the system. This software requires configuration before the database server is ready for use.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

If you are using DirectAdmin and you encounter any issues with Installing MariaDB with YUM, then the directions below may help. The process is very straightforward.

  httpd:
    Syntax error on line 18 of /etc/httpd/conf/httpd.conf:
    Syntax error on line 1 of /etc/httpd/conf/extra/httpd-phpmodules.conf:
      Cannot load /usr/lib/apache/libphp5.so into server:
        libmysqlclient.so.18: cannot open shared object file: No such file or directory

Or:

RPM Installation

To install the RPMs, there is a quick and easy guide to . Follow the instructions there.

Necessary Edits

We do not want DirectAdmin's custombuild to remove/overwrite our MariaDB installation whenever an update is performed. To rectify this, disable automatic MySQL installation.

Edit /usr/local/directadmin/custombuild/options.conf and replace mysql_inst=yes with mysql_inst=no

_{This page is licensed: CC BY-SA / Gnu FDL}

MariaDB RPM packages since are signed.

The key we use has an id of 1BB943DB and the key fingerprint is:

1993 69E5 404B D5FC 7D2F E43B CBCB 082A 1BB9 43DB

To check the signature you first need to import the public part of the key like so:

gpg --keyserver hkp://pgp.mit.edu --recv-keys 1BB943DB

Next you need to let pgp know about the key like so:

gpg --export --armour 1BB943DB > mariadb-signing-key.asc
sudo rpm --import mariadb-signing-key.asc

You can check to see if the key was imported with:

Once the key is imported, you can check the signature of the MariaDB RPM files by running the something like the following in your download directory:

The output of the above will look something like this (make sure gpg shows up on each OK line):

See Also

_{This page is licensed: CC BY-SA / Gnu FDL}

Binary tarballs (bintars) are compressed tar archives that contain pre-compiled executables, libraries, and other deployment dependencies. They can usually be installed on any modern Linux distribution.

MariaDB Binary tarballs are named following the pattern: mariadb-VERSION-OS.tar.gz. Be sure to the correct version for your machine.

Available RPM Packages

The available RPM packages depend on the specific MariaDB release series.

Available RPM Packages in MariaDB

The following RPMs are available in current versions of MariaDB:

Installing RPM Packages

Preferably, you should install MariaDB RPM packages using the package manager of your Linux distribution, for example yum orzypper. But you can also use the lower-level rpm tool.

Actions Performed by RPM Packages

Users and Groups Created

When the mariadb-server RPM package is installed, it will create a user and group named mysql, if it does not already exist.

See Also

_{This page is licensed: CC BY-SA / Gnu FDL}

MariaDB Corporation provides package repositories, including the MariaDB Enterprise Repository and the MariaDB Community Repository, that can be used to install MariaDB products using the operating system's package manager. Local mirrors of the package repositories can be used for local deployments.

Local package repository mirrors provide multiple benefits:

• MariaDB Corporation's official package repositories are the source for the local mirror.

• Tools provided by the operating system are used to create and maintain the local mirror.

• After a local mirror is created, the mirror can be used just like the MariaDB repositories to install MariaDB products using the operating system's package manager.

If you want to deploy MariaDB database products without using a local package repository mirror, are available. Available deployment methods are component-specific.

Use Cases

MariaDB database products can be deployed with local package repository mirrors to support use cases, such as:

• Install from the mirror on an air-gapped network that is not connected to the internet

• Remove packages from mirror for versions that are not used in the local environment

• Add packages to mirror for tools and clients that are used in the local environment

• Automatically install missing dependencies using a package manager

Compatibility

The following MariaDB database products can be deployed using package repositories:

• MariaDB ColumnStore 5 (included with MariaDB Community Server 10.5)

• MariaDB ColumnStore 6 (included with MariaDB Community Server 10.6)

• MariaDB Community Server 10.2

• MariaDB Community Server 10.3

Operating System Package Managers

The package manager depends on the operating system:

Create a Local Repository Mirror

Creating a local mirror of the MariaDB Enterprise Repository or the MariaDB Community Repository enables you to distribute MariaDB products to your servers from a local repository you support. Secure any such repository mirror to prevent outside access.

2. Set up a repository mirroring tool, for example:

   • YUM: reposync, available at:

   • APT: debmirror

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

This guide provides the detailed steps for installing MariaDB 10.1.21 via individual RPM packages on CentOS 7. The process involves installing dependencies, then the main packages, and resolving potential conflicts as they appear.

The RPMs needed for the installation are available from the MariaDB website. The required packages for this guide are:

Step-by-Step Installation

1. Install Basic Dependencies

First, use yum to install some general system packages that may be required.

2. Install MariaDB RPM Packages

Next, install the downloaded RPMs in sequence. Make sure to run these commands as a user with sufficient privileges (e.g., using sudo).

Troubleshooting Common Installation Errors and Warnings

Error 1: Package Conflict with mariadb-libs

Error 2: Failed Dependency for Galera

Warning: GPG Key NOKEY

Post-Installation

After all RPMs are successfully installed, the final step is to secure the server. This involves setting the root password, removing test databases, and disallowing remote root login.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB was originally designed as a drop-in replacement of MySQL, with more features, new storage engines, fewer bugs, and better performance, but you can also install it alongside MySQL. (This can be useful, for example, if you want to migrate databases/applications one by one.)

Here are the steps to install MariaDB near an existing MySQL installation.

• Download the compiled binary tar.gz file that contains the latest version.

• Extract the files in a directory of your choice. In the following, we assume you chose the /opt directory.

• Create data directory and symlinks as below:

• Create group mariadb and user mariadb and set correct ownerships:

• Create a new my.cnf in /opt/mariadb from support files:

• Edit the file /opt/mariadb-data/my.cnf and add custom paths, socket, port, user and the most important of all: data directory and base directory. Finally the file should have at least the following:

• Copy the init.d script from support files in the right location:

• Edit /etc/init.d/mariadb replacing mysql with mariadb as below:

The trickiest part will be the last changes to this file. You need to tell mariadb to use only one configuration file. In the start section after**$bindir/mysqld_safe** add --defaults-file=/opt/mariadb-data/my.cnf. Finally the lines should look like:

The same change needs to be made to the command below in the wait_for_ready() function so that the mariadb start command can properly listen for the server start. In the wait_for_ready() function, after $bindir/mariadb-admin add --defaults-file=/opt/mariadb-data/my.cnf. The lines should look like:

• Run by explicitly giving it the my.cnf file as argument:

• Now you can start MariaDB by

• Make MariaDB start at system start:

• Finally test that you have both instances running:

What about MariaDB Upgrades ?

By having the mariadb.socket, my.cnf file and databases in /opt/mariadb-data means that if you want to upgrade the MariaDB version you will only need to:

• Extract the new version from the archive in /opt near the current version,

• Stop MariaDB.

• Change the symlink mariadb to point to the new directory.

• Start MariaDB.

_{This page is licensed: CC BY-SA / Gnu FDL}

MariaDB Server is available for installation on macOS via the package manager. MariaDB Server (together with many client programs and helper tools) is available as a Homebrew "bottle", a precompiled package. If you haven't yet installed Homebrew, .

Installing & Starting MariaDB

Install MariaDB Server:

Start MariaDB Server:

Alternatively, and strongly recommended, automatically start MariaDB Server:

MSI packages is available for x64 (64 bit) processor architectures and, in some older releases only, for x86 (32 bit). We use screenshots from an x64 installation in the following.

Installation UI

This is the typical mode of installation. To start the installer, click on the mariadb-...msi.

On RHEL, CentOS, Fedora, and other similar Linux RPM based distributions, these provide MariaDB packages. These are supported by those distributions. If you have a particular need for a later version than what is in the distribution, then MariaDB provides repositories for them.

Using repositories rather than installing RPM allows for an ease of update when a new release is made. It is highly recommended to install the relevant from MariaDB's repository using or . Centos 7 still uses yum, most others use dnf, and SUSE/openSUSE use zypper.

This page walks you through the simple installation steps using dnf and yum.

On SLES, OpenSUSE, and other similar Linux distributions, it is highly recommended to install the relevant from MariaDB's repository using .

This page walks you through the simple installation steps using zypper.

Adding the MariaDB ZYpp repository

We currently have ZYpp repositories for the following Linux distributions:

Installing MariaDB with APT

On Debian, Ubuntu, and other similar Linux distributions, it is highly recommended to install the relevant .deb packages from MariaDB's repository using apt, aptitude, Ubuntu Software Center, Synaptic Package Manager, or another package manager.

This page walks you through the simple installation steps using apt.

Adding the MariaDB APT repository

We currently have APT repositories for the following Linux distributions:

• Debian 11 (Bullseye)

• Debian 12 (Bookworm)

• Debian 13 (Trixie)

• Debian Unstable (Sid)

Using the MariaDB Package Repository Setup Script

If you want to install MariaDB with apt, then you can configure apt to install from MariaDB Corporation's MariaDB Package Repository by using the .

MariaDB Corporation provides a MariaDB Package Repository for several Linux distributions that use apt to manage packages. This repository contains software packages related to MariaDB Server, including the server itself, , , , and . The MariaDB Package Repository setup script automatically configures your system to install packages from the MariaDB Package Repository.

To use the script, execute the following command:

Note that this script also configures a repository for and a repository for MariaDB Tools, which currently only contains and its dependencies.

See for more information.

Using the MariaDB Repository Configuration Tool

If you want to install MariaDB with apt, then you can configure apt to install from MariaDB Foundation's MariaDB Repository by using the .

The MariaDB Foundation provides a MariaDB repository for several Linux distributions that use apt-get to manage packages. This repository contains software packages related to MariaDB Server, including the server itself, , , , and . The MariaDB Repository Configuration Tool can easily generate the appropriate commands to add the repository for your distribution.

There are several ways to add the repository.

Executing add-apt-repository

One way to add an apt repository is by using the command. This command will add the repository configuration to /etc/apt/sources.list.

For example, if you wanted to use the repository to install on Ubuntu 18.04 LTS (Bionic), then you could use the following commands to add the MariaDB apt repository:

And then you would have to update the package cache by executing the following command:

Creating a Source List File

Another way to add an apt repository is by creating a file in /etc/apt/sources.list.d/.

For example, if you wanted to use the repository to install on Ubuntu 18.04 LTS (Bionic), then you could create the MariaDB.list file in /etc/apt/sources.list.d/ with the following contents to add the MariaDB apt repository:

And then you would have to update the package cache by executing the following command:

Using Ubuntu Software Center

Another way to add an apt repository is by using .

You can do this by going to the Software Sources window. This window can be opened either by navigating to Edit > Software Sources or by navigating to System > Administration > Software Sources.

Once the Software Sources window is open, go to the Other Software tab, and click the Add button. At that point, you can input the repository information provided by the .

See for more information.

Using Synaptic Package Manager

Another way to add an apt repository is by using .

You can do this by going to the Software Sources window. This window can be opened either by navigating to System > Administrator > Software Sources or by navigating to Settings > Repositories.

Once the Software Sources window is open, go to the Other Software tab, and click the Add button. At that point, you can input the repository information provided by the .

See for more information.

Pinning the MariaDB Repository to a Specific Minor Release

If you wish to pin the apt repository to a specific minor release, or if you would like to downgrade to a specific minor release, then you can create a apt repository with the URL hard-coded to that specific minor release.

The MariaDB Foundation archives repositories of old minor releases at the following URL:

Archives are only of the distros and architectures supported at the time of release. For example, exists for Ubuntu bionic, focal, jammy, kinetic, and #lunaris obtained looking in [dists](https://archive.mariadb.org/mariadb-10.6.21/repo/ubuntu/dists).

For example, if you wanted to pin your repository to on Ubuntu 20.04 LTS (Focal), then you would have to first remove any existing MariaDB repository source list file from /etc/apt/sources.list.d/. And then you could use the following commands to add the MariaDB apt-get repository:

Ensure you have the .

Ubuntu Xenial and older will need:

And then you would have to update the package cache by executing the following command:

Updating the MariaDB APT repository to a New Major Release

MariaDB's apt repository can be updated to a new major release. How this is done depends on how you originally configured the repository.

Updating the Major Release with the MariaDB Package Repository Setup Script

If you configured apt to install from MariaDB Corporation's MariaDB Package Repository by using the , then you can update the major release that the repository uses by running the script again.

Updating the Major Release with the MariaDB Repository Configuration Tool

If you configured apt to install from MariaDB Foundation's MariaDB Repository by using the , then you can update the major release in various ways, depending on how you originally added the repository.

Updating a Repository with add-apt-repository

If you added the apt repository by using the command, then you can update the major release that the repository uses by using the command again.

First, look for the repository string for the old version in /etc/apt/sources.list.

And then, you can remove the repository for the old version by executing the command and providing the --remove option. For example, if you wanted to remove a repository, then you could do so by executing something like the following:

After that, you can add the repository for the new version with the command. For example, if you wanted to use the repository to install on Ubuntu 18.04 LTS (Bionic), then you could use the following commands to add the MariaDB apt repository:

And then you would have to update the package cache by executing the following command:

After that, the repository should refer to and you can .

Updating a Source List File

If you added the apt repository by creating a file in /etc/apt/sources.list.d/, then you can update the major release that the repository uses by updating the source list file in-place. For example, if you wanted to change the repository from to , and if the source list file was at /etc/apt/sources.list.d/MariaDB.list, then you could execute the following:

And then you would have to update the package cache by executing the following command:

After that, the repository should refer to and you can .

Importing the MariaDB GPG Public Key

Before MariaDB can be installed, you also have to import the GPG public key that is used to verify the digital signatures of the packages in our repositories. This allows the apt utility to verify the integrity of the packages that it installs.

• Prior to Debian 9 (Stretch), and Debian Unstable (Sid), and Ubuntu 16.04 LTS (Xenial), the id of our GPG public key is 0xcbcb082a1bb943db. The full key fingerprint is:

The utility can be used to import this key. For example:

• Starting with Debian 9 (Stretch) and Ubuntu 16.04 LTS (Xenial), the id of our GPG public key is 0xF1656F24C74CD1D8. The full key fingerprint is:

The utility can be used to import this key. For example:

Starting with Debian 9 (Stretch), the package needs to be installed before the GPG public key can be imported. To install it, execute: sudo apt install dirmngr

If you are unsure which GPG public key you need, then it is perfectly safe to import both keys.

The command used to import the GPG public key is the same on both Debian and Ubuntu. For example:

Once the GPG public key is imported, you are ready to install packages from the repository.

Installing MariaDB Packages with APT

After the apt repository is configured, you can install MariaDB by executing the command. The specific command that you would use would depend on which specific packages that you want to install.

Installing the Most Common Packages with APT

To Install the most common packages, first you would have to update the package cache by executing the following command:

To Install the most common packages, execute the following command:

Installing MariaDB Server with APT

To Install MariaDB Server, first you would have to update the package cache by executing the following command:

Then, execute the following command:

Installing MariaDB Galera Cluster with APT

The process to install MariaDB Galera Cluster with the MariaDB apt-get repository is practically the same as installing standard MariaDB Server.

Galera Cluster support is included in the standard MariaDB Server packages, so you will need to install the mariadb-server package, as you normally would.

You also need to install the galera-4 package to obtain the 4 wsrep provider library.

To install MariaDB Galera Cluster, first you would have to update the package cache by executing the following command:

To install MariaDB Galera Cluster, you could execute the following command:

MariaDB Galera Cluster also has a separate package that can be installed on arbitrator nodes. The package is called galera-arbitrator-4. This package should be installed on whatever node you want to serve as the arbitrator. It can either run on a separate server that is not acting as a cluster node, which is the recommended configuration, or it can run on a server that is also acting as an existing cluster node.

To install the arbitrator package, you could execute the following command:

<>

See Galera for more information on MariaDB Galera Cluster.

Installing MariaDB Clients and Client Libraries with APT

is included as the client library.

To Install the clients and client libraries, first you would have to update the package cache by executing the following command:

Then, execute the following command:

Installing mariadb-backup with APT

To install , first you would have to update the package cache by executing the following command:

Then, execute the following command:

Installing Plugins with APT

Some may also need to be installed.

For example, to install the password validation plugin, first you would have to update the package cache by executing the following command:

Then, execute the following command:

Installing Older Versions from the Repository

The MariaDB apt repository contains the last few versions of MariaDB. To show what versions are available, use the command:

There will be a lot of output, but in the "Provides" section at the end of the output you will see the available versions. For example:

In the above example there are four versions available, two from the MariaDB repositories, and two from the Ubuntu repositories. The versions from MariaDB have "maria" in the version number, and the versions from Ubuntu have "ubuntu" in the version number.

To install an older version of a package instead of the latest version we just need to specify the package name, an equal sign, and then the complete version number. From the example above, the complete version number for MariaDB 12.0.2 is: 1:12.0.2+maria~ubu2404

However, when installing an older version of a package, apt will automatically choose to install the latest versions of any dependencies, which doesn't work for dependencies of the mariadb-server package like mariadb-client and mariadb-server-core.

To ensure that all MariaDB packages are on the same version in this scenario, it is necessary to specify them all. Therefore, to install the 12.0.2 version of the mariadb-server package from this apt repository, we would do the following (using a variable to hold the version number, and putting each package on its own line so things are cleaner):

For MariaDB Enterprise, version numbers are similar, but have an extra point. For example, MariaDB Enterprise Server 11.8.5-2 for Ubuntu 24.04 Noble has the version number: 1:11.8.5.2+maria~ubu2404 .

The rest of the install and setup process is as normal.

Installing MariaDB with dpkg

While it is not recommended, it is possible to download and install the.deb packages manually. However, it is generally recommended to use a package manager like apt-get.

A tarball that contains the .deb packages can be downloaded from the following URL:

For example, to install the .deb packages on Ubuntu 18.04 LTS (Bionic), you could execute the following:

After Installation

After the installation is complete, you can start MariaDB.

If you are using , then keep in mind that the first node will have to be .

Upgrading to a new version of MariaDB

After updating your repository configuration to move from the repository of one version of MariaDB to a newer version, as per the previous instructions, you will need to upgrade the MariaDB packages, this is done with:

Alternatively you can also run the following to installing the new version:

The reason for specifying the galera-4 package is to ensure the correct updated version of Galera is installed along with the new server version, replacing the versions that were there before.

Available DEB Packages

The available DEB packages depend on the specific MariaDB release series.

Available DEB Packages

For MariaDB, the following DEBs are available:

Actions Performed by DEB Packages

Users and Groups Created

When the mariadb-server DEB package is installed, it will create a user and group named mysql, if they do not already exist.

See Also

_{This page is licensed: CC BY-SA / Gnu FDL}

Overview

If you are looking to set up MariaDB Server, it is often easiest to use a repository. MariaDB Foundation has a repository configuration tool and MariaDB Corporation provides two convenient shell scripts to configure access to their MariaDB Package Repositories:

• mariadb_es_repo_setup for MariaDB Enterprise Server, which can be downloaded from:

• mariadb_repo_setup for MariaDB Community Server, which can be downloaded from:

Using MariaDB Foundation's Repository Configuration Tool

Visit and follow the instructions from there. It will ask for your Linux distribution, desired MariaDB version, and the mirror to use, and will show what files to edit and what commands to run to configure a repository.

Using MariaDB Corporation's Repository Setup Scripts

Alternatively, you can run a convenient shell script that will automatically configure a repository for you.

Download and Verify the Script

The repository setup script can be downloaded and verified in the following way:

Prerequisites

For the script to work, the curl package needs to be installed on your system. Additionally on Debian and Ubuntu the apt-transport-https package needs to be installed. The script will check if these are installed and let you know before it attempts to create the repository configuration on your system.

They can be installed on your system as follows:

Run the Script

After the script is downloaded you need to run it with root user permissions. This is normally accomplished by using the sudo command:

Repositories

The script will set up different repositories in a single repository configuration file.

The default repositories setup by mariadb_es_repo_setup are:

• MariaDB Enterprise Server Repository

  • A MariaDB Enterprise Server Debug Repository (Ubuntu only)

• MariaDB Enterprise MaxScale Repository

• MariaDB Enterprise Tools Repository

The default repositories set up by mariadb_repo_setup are:

• MariaDB Community Server Repository

• MariaDB Community Server Debug Repository (Ubuntu only)

• MariaDB MaxScale Repository

• MariaDB Tools Repository

MariaDB Community Server Repository

The MariaDB Community Server Repository contains software packages related to MariaDB Server, including the server itself, , , , and .

The binaries in MariaDB Corporation's MariaDB Repository are identical to the binaries in MariaDB Foundation's MariaDB Repository that is configured with the .

By default, the mariadb_repo_setup script will configure your system to install from the 12.rolling repository, which contains the latest stable version of MariaDB Community server.

The mariadb_es_repo_setup script will set up the current latest stable version of MariaDB Enterprise Server.

If you would like to stick to a specific release series, then you will need to either manually edit the repository configuration file to point to that specific version or series, or run the MariaDB Package Repository setup script again using the --mariadb-server-version option. For example, if you wanted to specifically use the 11.4 series you would do: --mariadb-server-version=11.4.

If you do not want to configure the MariaDB Repository on your system, for example if you are setting up a server just running MariaDB MaxScale, then you can use the --skip-server option to prevent the setup script from configuring the server repository.

MariaDB MaxScale Repository

The MariaDB MaxScale Repository contains software packages related to .

By default, the script will configure your system to install from the repository of the latest GA version of MariaDB MaxScale. When a new major GA release occurs, the repository will automatically switch to the new version. If instead you would like to stay on a particular version you will need to manually edit the repository configuration file and change 'latest' to the version you want (e.g. '6.1') or run the MariaDB Package Repository setup script again, specifying the particular version or series you want.

Older versions of the MariaDB Package Repository setup script would configure a specific MariaDB MaxScale series in the repository (i.e. 24.02), so if you used the script in the past to set up your repository and want MariaDB MaxScale to automatically use the latest GA version then change 24.02 or whatever version it is set to in the repository configuration to latest. Or download the current version of the setup script and re-run it to set up the repository again.

The script can configure your system to install from the repository of an older version of MariaDB MaxScale if you use the --mariadb-maxscale-version option. For example, --mariadb-maxscale-version=25.01 .

If you do not want to configure the MariaDB MaxScale Repository on your system, then you can use the --skip-maxscale option to prevent the setup script from configuring it.

Supported Distributions

The script supports Linux distributions that are officially supported by MariaDB Corporation's . However, a MariaDB TX subscription with MariaDB Corporation is not required to use the MariaDB Package Repository.

The distributions currently supported by the script include:

• Red Hat Enterprise Linux (RHEL and equivalents) 8, 9, and 10

• Debian 11 (Bullseye), 12 (Bookworm), and 13 (Trixie, community server only)

• Ubuntu 22.04 LTS (Jammy), and 24.04 LTS (Noble)

• SUSE Linux Enterprise Server (SLES) 15

To install MariaDB on distributions not supported by the MariaDB Package Repository setup script, please consider using MariaDB Foundation's . Some Linux distributions also include MariaDB .

Options

To provide options to the script, you must tell your to expect them by executing bash with the options -s --, for example:

--mariadb-server-version

By default, the script will configure your system to install from the repository of the latest GA version of MariaDB. If a new major GA release occurs and you would like to upgrade to it, then you will need to either manually edit the repository configuration file to point to the new version, or run the MariaDB Package Repository setup script again.

The script can also configure your system to install from the repository of a different version of MariaDB if you use the --mariadb-server-version option.

The string mariadb- has to be prepended to the version number. For example, to configure your system to install from the repository of MariaDB 11.8, that would be:

The following MariaDB versions are currently supported:

• mariadb-10.6

• mariadb-10.11

• mariadb-11.4

• mariadb-11.8

If you want to pin the repository of a specific minor release, such as MariaDB 11.8.5, then you can also specify the minor release. For example,mariadb-10.8.5. This may be helpful if you want to avoid upgrades. However, avoiding upgrades is not recommended, since minor maintenance releases may contain important bug fixes and fixes for security vulnerabilities.

--mariadb-maxscale-version

By default, the script will configure your system to install from the repository of the latest GA version of MariaDB MaxScale.

If you would like to pin the repository to a specific version of MariaDB MaxScale then you will need to either manually edit the repository configuration file to point to the desired version, or use the --mariadb-maxscale-version option.

For example, to configure your system to install from the repository of MariaDB MaxScale 6.1, that would be:

The following MariaDB MaxScale versions are currently supported:

• MaxScale 25.10

• MaxScale 25.01

• MaxScale 24.02

• MaxScale 23.08

The special identifiers latest (for the latest GA release) and beta (for the latest beta release) are also supported. By default themariadb_repo_setup script uses latest as the version.

--os-type and --os-version

If you want to run this script on an unsupported OS that you believe to be package-compatible with an OS that is supported, then you can use the--os-type and --os-version options to override the script's OS detection. If you use either option, then you must use both options.

The supported values for --os-type are:

• rhel

• debian

• ubuntu

• sles

If you use a non-supported value, then the script will fail, just as it would fail if you ran the script on an unsupported OS.

The supported values for --os-version are entirely dependent on the OS type.

For Red Hat Enterprise Linux (RHEL): 8, 9, and 10 are valid options.

For Debian and Ubuntu, the version must be specified as the codename of the specific release. For example, Debian 13 must be specified as trixie, and Ubuntu 24.04 must be specified as noble.

These options can be useful if your distribution is a fork of another distribution. As an example, Pop!_OS 24.04 LTS is based on and is fully compatible with Ubuntu 24.04 LTS (noble). Therefore, If you are using Pop!_OS, then you can configure your system to install from the repository of Ubuntu 24.04 LTS (noble) by specifying --os-type=ubuntu --os-version=noble to the MariaDB Package Repository setup script.

For example, to manually set the --os-type and --os-version to RHEL 10 you could do:

--write-to-stdout

The --write-to-stdout option will prevent the script from modifying anything on the system. The repository configuration will not be written to the repository configuration file. Instead, it will be printed to standard output. That allows the configuration to be reviewed, redirected elsewhere, consumed by another script, or used in some other way.

The --write-to-stdout option automatically enables --skip-key-import.

For example:

Platform-Specific Behavior

Installing Packages With the MariaDB Package Repository

After setting up the MariaDB Package Repository, you can install the software packages in the supported repositories.

Versions