MariaDB Package Repository Setup and Usage
Overview
If you are looking to set up MariaDB Server, it is often easiest to use a repository. The 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_setupfor MariaDB Enterprise Server, which can be downloaded from:mariadb_repo_setupfor MariaDB Community Server, which can be downloaded from:
Download and Verify the script
The repository setup script can be downloaded and verified in the following way:
Download the script:
Verify the checksum of the script:
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:
Retrieve your customer downloads token:
Log in
Copy the Customer Download Token
Substitute your token for
${token}when running themariadb_es_repo_setupscript, below
Set the script to be executable:
Run the script:
Repositories
The script will will set up different repositories in a single repository configuration file. The primary two are the MariaDB Server Repository, and the MariaDB MaxScale Repository.
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 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 Server Repository
The MariaDB Repository contains software packages related to MariaDB Server, including the server itself, clients and utilities, client libraries, plugins, and Mariabackup.
The binaries in MariaDB Corporation's MariaDB Repository are currently identical to the binaries in MariaDB Foundation's MariaDB Repository that is configured with the MariaDB Repository Configuration Tool.
By default, the mariadb_repo_setup script will configure your system to install from the 11.rolling repository, which contains the latest stable version of MariaDB Community server.
The mariadb_es_repo_setup script will set up whatever is the current 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 MariaDB MaxScale.
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 MariaDB TX subscription. 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) 8, and 9
Debian 10 (Buster), 11 (Bullseye), 12 (Bookworm)
Ubuntu 20.04 LTS (Focal), 22.04 LTS (Jammy), and 24.04 LTS (Noble)
SUSE Linux Enterprise Server (SLES) 12 and 15
To install MariaDB on distributions not supported by the MariaDB Package Repository setup script, please consider using MariaDB Foundation's MariaDB Repository Configuration Tool. Some Linux distributions also include MariaDB in their own repositories.
Options
To provide options to the script, you must tell your to expect them by executing bash with the options -s --, for example:
--help
Display a usage message and exit
--mariadb-server-version=
Override the default MariaDB Server version. By default, the script will use '11.rolling'
--mariadb-maxscale-version=
Override the default MariaDB MaxScale version. By default, the script will use 'latest'
--os-type=
Override detection of OS type. Acceptable values include debian, ubuntu, rhel, and sles
--os-version=
Override detection of OS version. Acceptable values depend on the OS type you specify
--skip-key-import
Skip importing GPG signing keys
--skip-maxscale
Skip the 'MaxScale' repository
--skip-server
Skip the 'MariaDB Server' repository
--skip-tools
Skip the 'Tools' repository
--skip-verify
Skip verification of MariaDB Server versions. Use with caution as this can lead to an invalid repository configuration file being created
--skip-check-installed
Skip tests for required prerequisites for this script
--skip-eol-check
Skip tests for versions being past their EOL date
--skip-os-eol-check
Skip tests for operating system versions being past EOL date
--write-to-stdout
Write output to stdout instead of to the OS's repository configuration file. This will also skip importing GPG public keys and updating the package cache on platforms where that behavior exists
--mariadb-server-version
--mariadb-server-versionBy 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 10.6, that would be:
The following MariaDB versions are currently supported:
mariadb-10.5mariadb-10.6mariadb-10.11mariadb-11.4mariadb-11.7mariadb-11.8mariadb-11.rollingmariadb-11.rc
If you want to pin the repository of a specific minor release, such as MariaDB
10.6.14, then you can also specify the minor release. For example,mariadb-10.6.14. 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
--mariadb-maxscale-versionBy 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 1.4
MaxScale 2.0
MaxScale 2.1
MaxScale 2.2
MaxScale 2.3
MaxScale 2.4
MaxScale 2.5
MaxScale 6.1
MaxScale 6.2
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
--os-type and --os-versionIf 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:
rheldebianubuntusles
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) and CentOS, 7 and 8 are valid
options.
For Debian and Ubuntu, the version must be specified as the codename of the
specific release. For example, Debian 9 must be specified as stretch, and
Ubuntu 18.04 must be specified as bionic.
These options can be useful if your distribution is a fork of another
distribution. As an example, Linux Mint 8.1 is based on and is fully compatible
with Ubuntu 16.04 LTS (Xenial). Therefore, If you are using Linux Mint 8.1,
then you can configure your system to install from the repository of Ubuntu
16.04 LTS (Xenial). If you would like to do that, then you can do so by
specifying --os-type=ubuntu and --os-version=xenial to the MariaDB
Package Repository setup script.
For example, to manually set the --os-type and --os-version to RHEL 8
you could do:
--write-to-stdout
--write-to-stdoutThe --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
Platform-Specific Behavior on RHEL and CentOS
On Red Hat Enterprise Linux (RHEL) and CentOS, the MariaDB Package Repository setup script performs the following tasks:
Creates a repository configuration file at
/etc/yum.repos.d/mariadb.repo.Imports the GPG public key used to verify the signature of MariaDB software packages with
rpm --importfromdownloads.mariadb.com.
Platform-Specific Behavior on Debian and Ubuntu
On Debian and Ubuntu, the MariaDB Package Repository setup script performs the following tasks:
Creates a repository configuration file at
/etc/apt/sources.list.d/mariadb.list.Creates a package preferences file at
/etc/apt/preferences.d/mariadb-enterprise.pref, which gives packages from MariaDB repositories a higher priority than packages from OS and other repositories, which can help avoid conflicts. It looks like the following:
Imports the GPG public key used to verify the signature of MariaDB software package with
apt-keyfrom thekeyserver.ubuntu.comkey server.Updates the package cache with package definitions from the MariaDB Package Repository with
apt-get update.
Platform-Specific Behavior on SLES
On SUSE Linux Enterprise Server (SLES), the MariaDB Package Repository setup script performs the following tasks:
Creates a repository configuration file at
/etc/zypp/repos.d/mariadb.repo.Imports the GPG public key used to verify the signature of MariaDB software packages with
rpm --importfromdownloads.mariadb.com.
Installing Packages with the MariaDB Package Repository
After setting up the MariaDB Package Repository, you can install the software packages in the supported repositories.
Installing Packages on RHEL and CentOS
To install MariaDB on Red Hat Enterprise Linux (RHEL) and CentOS, see the instructions at Installing MariaDB Packages with YUM. For example:
To install MariaDB MaxScale on Red Hat Enterprise Linux (RHEL) and CentOS, see the instructions at MariaDB MaxScale Installation Guide. For example:
Installing Packages on Debian and Ubuntu
To install MariaDB on Debian and Ubuntu, see the instructions at Installing MariaDB Packages with APT. For example:
To install MariaDB MaxScale on Debian and Ubuntu, see the instructions at MariaDB MaxScale Installation Guide. For example:
Installing Packages on SLES
To install MariaDB on SUSE Linux Enterprise Server (SLES), see the instructions at Installing MariaDB Packages with ZYpp. For example:
To install MariaDB MaxScale on SUSE Linux Enterprise Server (SLES), see the instructions at MariaDB MaxScale Installation Guide. For example:
Versions
mariadb_es_repo_setup Versions
Version
sha256sum
2025-06-04
4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0
2025-01-16
99ea6c55dbf32bfc42cdcd05c892aebc5e51b06f4c72ec209031639d6e7db9fe
2025-01-07
b98c6436e01ff33d7e88513edd7b77a965c4500d6d52ee3f106a198a558927af
2024-11-19
97e5ef25b4c4a4bd70b30da46b1eae0b57db2f755ef820a28d254e902ab5a879
2024-11-13
0c181ada4e7a4cd1d7688435c478893502675b880be2b918af7d998e239eb325
2024-09-20
c12da6a9baa57eab7fa685aa24bf76e6929a8c67f4cd244835520c0181007753
2024-09-09
733f247c626d965304b678b62a4b86eb4bb8bf956f98a241b6578dedc6ca4020
2024-06-12
b96fcd684a84bbe1080b6276f424537fc9d9c11ebe243ad8b9a45dd459f6ee4f
2023-07-27
f8eb9c1b59ccfd979d27e39798d2f2a98447dd29e2149ce92bf606aab4493ad9
2023-03-13
8dfef0ec98eb03a4455df07b33107a6d4601425c9df0ab5749b8f10bf3abdcbb
2022-10-26
3f4a9d1c507a846a598e95d6223871aade69a9955276455324e7cc5f54a87021
2022-09-12
713a8f78ea7bab3eccfb46dc14e61cd54c5cf5a08acb5c320ef5370d375e48bd
2022-06-14
cfcd35671125d657a212d92b93be7b1f4ad2fda58dfa8b5ab4b601bf3afa4eae
2022-03-11
53efddb84ea12efa7d521499a7474065bd4a60c721492d0e72b4336192f4033f
2021-12-13
5feb2aac767c512cc9e2af674d1aef42df0b775ba2968fffa8700eb42702bd44
2021-10-13
4f266ff758fe15eeb9b8b448a003eb53e93f3064baf1acb789dd39de4f534b1d
2021-09-14
b741361ea3a0a9fcaa30888a63ff3a8a4021882f126cf4ef26cf616493a29315
2021-08-26
a49347a4e36f99c5b248403ed9fb9b33a2f07f5e24605a694b1b1e24d7199f28
2021-06-29
99e768b24ae430b37dec7cb69cdd625396630dba18f5e1588ee24d3d8bb97064
2021-06-14
ec08f8ede524f568b3766795ad8ca1a0d0ac4db355a18c3d85681d7f9c0f8c09
2021-05-04
bf67a231c477fba0060996a83b197c29617b6193e1167f6f062216ae13c716c7
2021-03-15
99c7f4a3473a397d824d5f591274c2a4f5ebf6dc292eea154800bbaca04ddc7e
2021-02-12
c78db828709d94876406a0ea346f13fbc38e73996795903f40e3c21385857dd4
2020-12-16
c01fa97aed71ca0cd37cba7036ff80ab40efed4cc261c890aa2aa11cd8ab4e2f
2020-12-15
e42f1f16f2c78a3de0e73dcc2a9081e2f771b3161f4f4ceecb13ea788d84673b
2020-12-14
4aaf495606633a47c55ea602829e67e702aec0a5c6ff6b1af90709c19ee9f322
2020-10-07
93fa0df3d6491a791f5d699158dcfe3e6ce20c45ddc2f534ed2f5eac6468ff0a
2020-09-08
eeebe9e08dffb8a4e820cc0f673afe437621060129169ea3db0790eb649dbe9b
2020-07-16
957bc29576e8fd320fa18e35fa49b5733f3c8eeb4ca06792fb1f05e089c810ff
This page is licensed: CC BY-SA / Gnu FDL
Last updated
Was this helpful?