The Latest Packages

Tarballs, binaries (Linux, Solaris, and Windows), and packages for some Linux distributions are available at mariadb.com/downloads/ or mariadb.org/download/ (which also contains a PDF version of the MariaDB Server documentation).

We hope that interested community package maintainers will step forward, as others already have, to build packages for their distributions. We ask for strict adherence to your packaging system's best practices and invite you to create a bug report if our project impedes this in any way.

Instructions how to install the packages can be found here.

Distributions Which Include MariaDB

• Most distributions already include MariaDB. See .

Pre-Release Binaries

Binaries from our system (see also the page), are available at . They are not suitable for use in production systems but may be of use for debugging.

Once at the above URL you will need to click on the MariaDB tree you are interested in, and then the build. The build number corresponds to thetarbuildnum variable in Buildbot.

For example, if you were interested in the bsd9-64 build of the tree, revision 3497, the tarbuildnum is listed in the "Build Properties" table of the . In this case, the value is "2434".

Getting the Source

You can find all the source code at

To retrieve the code, the source control software offers the path of least resistance. If you are unfamiliar with git, please refer to the for an understanding of version control with git.

For instructions on creating a local branch of MariaDB, see the page.

See the page for general instructions on compiling MariaDB from the source. The page has links to platform and distribution-specific information, including information on how we build the release packages.

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

Packages for Fedora Linux are included with our other packages available for download on.

We have also added YUM repositories to our online .

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

Latest Packages

Tarballs, source and binaries (Linux and Windows), and packages for some Linux distributions are available at mariadb.org/download.

We hope that interested community package maintainers will step forward, as others already have, to build packages for their distributions. We ask for strict adherence to your packaging system's best practices and invite you to create a bug report if our project impedes this in any way.

Instructions how to install the packages can be found here. See the documentation page for a list of which Linux distributions that include MariaDB.

Pre-Release Binaries

Binaries from our system at are available as containers on quay.io/mariadb-foundation/mariadb-devel:{major version}. Tags available are listed .

These haven't passed through a full release process; however changes there have been reviewed and are considered complete by the server developers. Its recommend to use these for testing.

Getting the Source

The download page contains the source for all released binaries. You can find the latest source code at

To retrieve the code, the source control software offers the path of least resistance. If you are unfamiliar with git, please refer to the for an understanding of version control with git.

For instructions on creating a local branch of MariaDB, see the page.

See the page for general instructions on compiling MariaDB from the source. The page has links to platform and distribution-specific information, including information on how we build the release packages.

Old Versions

Running the is generally the best choice. Note that there are long-term releases, maintained for five years, short-term releases, maintained for one year, and rolling releases. However, some organizations still use old or very old versions of MariaDB. An upgrade would probably require important changes in their applications, and sometimes they don't even have the sources of those applications.

contains all historical releases.

There are source and repositories there. To use repositories see the following link:

It is also possible to access Docker Official Images of MariaDB back to 5.5.40 when it became an official image ().

Checking out the Source with Git

The MariaDB source is hosted on GitHub: server. You can get a copy with:

If you want a source tarball for a specific released MariaDB version, you can find it at downloads.mariadb.org.

At any given time, developers is working on their own branches locally or on GitHub, with the main MariaDB branches receiving pushes less often.

The main MariaDB branches are:

Source repositories for the MariaDB Connectors are:

See also:

• page for instructions on how to use git to check out the source code and switch between the various branches.

The instructions on this page will help you download your own local branch of the MariaDB source code repository with the full revision history. If you want a tarball of the source without the revision history, see the .

Checking out the Source with Bazaar

If you simply want to browse the source code, you can do so from .

Prerequisites

You need for revision control.

Instructions

1. Prepare a directory to keep your MariaDB code in:

1. Get a clean local copy of the Maria repo with:

The above will give you the latest stable MariaDB version. If you want to get another release use lp:maria/5.2, lp:maria/5.3... For a complete list, go to and choose from the top menu on the page.

• Note: The initial branch operation can take a long time depending on the speed of your Internet connection and the load on launchpad. For this initial branch you need to download over a gigabyte of data.

• Note: Bzr is written in Python and very slow for initial checkout. Even on a fast connection, expect to need 1-2 GByte of RAM and possibly several CPU hours for the checkout.

1. If you get an error like:

then the version of bzr you are using is too old. Using or higher will fix this error.

1. If you have upgraded your bzr and are unable to successfully branch from launchpad, try using the source tree tarball (below) instead.

2. You can see the current history with:

1. If you are going to be hacking on the MariaDB source code. See the page for help.

2. If you just want to compile MariaDB at this point, see the page.

Source Tree Tarball

For those that have trouble branching MariaDB from Launchpad we have created a tarball of a complete repository of the MariaDB tree.

Prerequisites

You need to work with the repository.

Using the Source Tree Tarball

1. Download the mariadb-shared-repo.tgz file from .

• The file is 267MB, so the download may take a long time to complete depending on your Internet connection.

1. The .tgz file contains a .bzr directory. The parent directory of this .bzr directory is (or becomes) a shared repository containing the MariaDB source code. It is recommended to create a new directory for this, so the next step is to create a directory to house the repository. Call this directory anything you like ("maria", "mariadb", "my", "src", etc...). Once created, cd into the directory and untar the file. Here is an example using the name "mariadb" for the new directory, with the directory located in a directory called "src" in the home directory of the current user, and the mariadb-shared-repo.tgz file located in a directory named Downloads (also in the current user's home directory):

1. After the untar step you will have a bzr shared repository, but not a working tree. While in the shared repository directory, use thebzr branch command to branch the MariaDB trees you are interested in. For example:

• bzr branch lp:maria/5.2

• bzr branch lp:maria

1. Thanks to the repository, either of the above commands will complete very fast.

2. Before working with the code, make sure you pull down the latest version of the source code:

1. You can now use this source tree as if you had branched it from launchpad directly.

Alternate Bazaar Instructions

The following alternative instructions are what we have used for setting up repositories on our build machines in .

Shell Variables

To streamline later steps, we start by setting several shell variables. Set the values of the BZR and WORK_DIR variables to the appropriate values for your Linux distribution. The rest of the variables in this section should not need to be changed.

Binaries:

Directories

Source Checkout

Initialize your bzr working directories, if not done already:

Check out MariaDB sources:

Check out packaging sources (only for and below):

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

We rely on mirrors to distribute MariaDB to the world through the official download site at download. If you would like to volunteer to become a mirror, thank you! Getting you set up is easy.

How to Become a MariaDB Mirror

The only requirements for becoming a mirror are:

1. A willingness to mirror MariaDB

2. Mirroring is done using rsync

3. An https mirror should be utilised (http mirrors are not accepted any more)

4. Available bandwidth and disk space

Updating Notes

MariaDB will normally have no more than one release per series (10.4, 10.5, etc...) per month. There may be times when this is not the case (such as if a major bug is found), but those times are few.

Timing for release announcements is generally oriented to the U.S. Eastern time zone. So if your mirror only updates less frequently than every 6 hours, have it update after midnight, but before 06:00, U.S. Eastern Time.

With rsync, it is no problem to update several times per day, and doing so is encouraged.

rsync Information

The two primary rsync URLs for mirrors to use are:

USA:

Europe:

Here are suggested rsync commands for a mirror to use:

Be aware that when using the above rsync command, a "mariadb" directory will not be created. Instead, the contents of the mariadb module is rsynced into whatever local folder you specify. We suggest creating a "mariadb" folder for this.

It is also a good idea to test your rsync command before adding it to a cron job by adding the -v --dry-run flags to the command temporarily so you can see what it will do (without actually doing anything).

As of June 2025, running the above command will use around 750GB of disk space in total.

See the for details on what each of the arguments in the command above does.

Secondary rsync mirrors

We also have several secondary rsync mirrors you can pull from. In many instances pulling from the secondary mirror is faster than pulling from the primary rsync mirrors. Here they are, with the country they are located in. Simply replace the rsync URI in the example above with one from this list to use it.

The MariaDB Foundation mirrorbits system

The MariaDB Foundation maintains a mirror manager system (see: ). It is hosted by Hetzner in Germany, it is not available via rsync so you can't use it as a source for your mirror but you are encouraged to use it for your MariaDB installation and deployments. You can check the status of the service at https://mirror.mariadb.org/mirrorstats.

Getting Added to the Mirror List

Once you have initially mirrored the MariaDB release tree, please send an email to (mirror (at) mariadb [dot] org) with the following information:

1. The name of the company or organization sponsoring the mirror (so we can give credit where credit is due).

2. Contact name (and email address) for your mirror (so we know who to contact if there are any issues)

3. The general physical location (e.g. "Paris, France", "Hong Kong", or "Austin, Texas, USA") of the mirror (we use geolocation to try and send people to a mirror close to them).

4. The base public URL for the mirror (e.g. 'http://mirror.example.net/pub/mariadb'

Once we receive your email and verify your mirror is working we'll add you to the list of mirrors. Apologies in advance in case of slow responses - mirror updates are usually batched around release time.

Thank you for volunteering to mirror MariaDB!

Credits

The primary MariaDB mirrors have been generously provided by the (at rsync.osuosl.org) and (at mirror.netcologne.de).

Other mirrors (list not necessarily complete) are listed below and can be selected on the site:

Global (CDN)

• CICKU (Global - CloudFlare)

Australia

• AARNet (Brisbane)

• Digital Pacific (Sydney)

• Real World Group (Sydney)

Austria

• Alwyzon (Vienna)

• Digital Nova (Graz)

• Kumi Systems e.U (Vienna)

• next layer GmbH (Vienna)

Azerbaijan

• YER Hosting

Bulgaria

• Neterra Telecommunications

Canada

• ACORN-NS (Halifax)

Chile

• Insacom (Valparaíso)

China - 中国

• Dalian Neusoft University of Information / 大连东软信息学院 (Dalian)

• 清华大学 TUNA 协会 - Tsinghua University TUNA Association (Beijing)

• 中国科学技术大学, 合肥 - USTC (Hefei)

• eScience Center, Nanjing University (南京大学)

Czech Republic

• HOSTING90 systems (Prague)

• vpsFree.cz

Denmark

• dotsrc.org - Aalborg University (Aalborg)

• Group.one (Copenhagen)

Estonia

• xTom GmbH (Tallinn)

France

• IRCAM, Institut de recherche et coordination acoustique/musique (Paris)

• OVH (Roubaix)

Germany

• 23media (Frankfurt)

• AG DSN (Dresden)

• creoline GmbH (Frankfurt am Main)

• dogado GmbH (Leipzig)

Greece

• University of Crete / Computer Center (Crete, Heraklion)

Hong Kong

• 網匯在線有限公司 - Nethub Online Limited

• xTom GmbH (Hong Kong)

Hungary

• Budapest University of Technology and Economics (Budapest)

India

• Bharat Datacenter (New Delhi)

• Indian Institute Of Technology Delhi (New Delhi)

Indonesia

• Universitas Surabaya (Surabaya)

• Citrahost By Citranet (Jakarta)

• Heru Nugroho (Jakarta)

• Nevacloud (Jakarta)

Iran

• Kernel.ir (Tehran)

• Mobinhost (Tehran)

• Parsvds (Tehran)

Ireland

• HEAnet Ltd. (Dublin)

Israel

• SPD Hosting LTD (Rosh Haayin)

Italy

• EvoWise (Milan)

Japan

• 山形大学, 米沢市 - Yamagata University (Yonezawa)

• xTom GmbH (Osaka)

• KuronekoServer (Tokyo)

Kenya

• Liquid Telecom (Nairobi)

Lithuania

• UAB "Interneto Vizija" (Vilnius)

Moldova

• ihost.md (Chisinau)

• MangoHost.NET (Chisinau)

Morocco

• Marwan

The Netherlands

• bouwhuis.network (Amsterdam)

• NLUUG (Amsterdam)

• Serverion.com (Zoetermeer)

• Triple IT B.V.

Norway

• FjordOS (Oslo)

Philippines

• RISE

Poland

• ICM UW (Interdisciplinary Centre for Modelling, Warsaw University)

Portugal

• PTISP (Lisbon)

• WebHS (Lisbon)

• Universidade do Porto

Romania

• Chroot Network (Bucharest)

• nxtHost.com (Bucharest)

Russia

• docker.ru (Moscow)

• МИФИ - National Research Nuclear University "MEPhI" (Moscow)

• Truenetwork (Novosibirsk)

Singapore

• Daan van Gorkum

• National University of Singapore

South Korea

• zzunipark (Gwangju, South Korea)

Spain

• Raiola Networks (Madrid)

Switzerland

• MvA Internet Services GmbH (Zurich)

Taiwan

• OSSPlanet + Ubuntu-TW - Ubuntu 台灣在地推廣組

• Blendbyte (Taipei)

Thailand

• Khon Kaen University (Khon Kaen)

• THZHost.com (Bangkok)

Ukraine

• Distrohub (Kyiv)

• mirohost.net (Kyiv)

The United States of America (USA)

• Accretive Networks (Washington, Seattle)

• EvoWise (California, Los Angeles)

• EvoWise (New York, New York)

• Gigenet (Chicago, Illinois)

Uruguay

• Universidad de la República - Facultad de Derecho (Montevideo)

Vietnam

• BKNS.VN (Hanoi)

The MariaDB Archive

The distributed mirrors above only hold the most recent 3-4 releases of each MariaDB series (10.6, 10.11, etc...). If you need to access older MariaDB releases, there is an archive server that contains every MariaDB release. This server is available via the web at and via rsync at:

Mirroring the MariaDB Archive with rsync

If you want to mirror the archive mirror, please contact us at mirror@mariadb.org in advance.

To mirror the archive with rsync, something like the following will get you everything:

...or you can specify a specific release such as:

Warning, as of June 2025, the entire archive will use around 14 TB of disk space in total, and if you want to keep your mirror up to date (via cron routine for instance), please first compare the STATUS file before doing the rsync. This file is updated anytime a new content is added in the archive tree.

You can use something like the following:

We reserve the right to block IPs that continually rsync the archive mirror when no new content was added, since it uselessly overloads the archive server, which uses a slow remote storage system.

To get a listing of the top level items in the archive including a list of every MariaDB release, just do:

If you would like to become a full archive mirror of MariaDB and be listed here, just let us know via the . Thanks!

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