hub.docker.com Open in urlscan Pro
2600:1f18:2148:bc02:a090:6a5b:b2ff:3152 Public Scan

Back to summary

URL:
https://hub.docker.com/_/mariadb/
Submission: On May 30 via api (May 30th 2024, 5:02:16 pm UTC) from US — Scanned from DE

Form analysis
1 forms found in the DOM

GET /search

<form class="MuiBox-root css-11qjisw" method="get" action="/search">
  <div class="MuiAutocomplete-root MuiAutocomplete-fullWidth css-18n1eq3">
    <div class="MuiFormControl-root MuiFormControl-marginDense MuiFormControl-fullWidth MuiTextField-root  css-1ikt25y" data-testid="autocompleteInput">
      <div class="MuiInputBase-root MuiOutlinedInput-root MuiInputBase-colorPrimary MuiInputBase-fullWidth MuiInputBase-formControl MuiInputBase-sizeSmall MuiInputBase-adornedStart MuiInputBase-adornedEnd MuiAutocomplete-inputRoot css-17nw5z4">
        <div class="MuiInputAdornment-root MuiInputAdornment-positionStart MuiInputAdornment-outlined MuiInputAdornment-sizeSmall css-1fm2mod"><span class="notranslate"></span><svg class="MuiSvgIcon-root MuiSvgIcon-fontSizeMedium css-14yq2cq"
            focusable="false" aria-hidden="true" viewBox="0 0 24 24" data-testid="SearchIcon">
            <path d="M15.5 14h-.79l-.28-.27C15.41 12.59 16 11.11 16 9.5 16 5.91 13.09 3 9.5 3S3 5.91 3 9.5 5.91 16 9.5 16c1.61 0 3.09-.59 4.23-1.57l.27.28v.79l5 4.99L20.49 19zm-6 0C7.01 14 5 11.99 5 9.5S7.01 5 9.5 5 14 7.01 14 9.5 11.99 14 9.5 14">
            </path>
          </svg></div><input aria-invalid="false" autocomplete="off" id=":r0:" name="q" placeholder="Search Docker Hub" type="text"
          class="MuiInputBase-input MuiOutlinedInput-input MuiInputBase-inputSizeSmall MuiInputBase-inputAdornedStart MuiInputBase-inputAdornedEnd MuiAutocomplete-input MuiAutocomplete-inputFocused css-1xn85km" aria-autocomplete="list"
          aria-expanded="false" autocapitalize="none" spellcheck="false" role="combobox" value="">
        <div class="MuiInputAdornment-root MuiInputAdornment-positionEnd MuiInputAdornment-outlined MuiInputAdornment-sizeSmall css-41g03h">
          <div class="MuiBox-root css-j3iiqs">ctrl+K</div>
        </div>
        <fieldset aria-hidden="true" class="MuiOutlinedInput-notchedOutline css-16zz1in">
          <legend class="css-ihdtdm"><span class="notranslate"></span></legend>
        </fieldset>
      </div>
    </div>
  </div>
  <div role="presentation" class="base-Popper-root MuiAutocomplete-popper css-1le80r3" style="position: fixed; top: 0px; left: 0px; display: none; width: 519px;">
    <div class="MuiPaper-root MuiPaper-elevation MuiPaper-rounded MuiPaper-elevation4 MuiAutocomplete-paper css-1sd661p"></div>
  </div>
</form>

Text Content

docker
Hub

ctrl+K

Help

Sign InSign up
1. Explore
2. /
3. Official Images
4. /

5. mariadb

MARIADB

Docker Official Image
•

1B+

•
5.8K

MariaDB Server is a high performing open source relational database, forked from
MySQL.

Databases & Storage
docker pull mariadb

Copy
OverviewTags

QUICK REFERENCE

* Maintained by:
MariaDB Foundation, MariaDB plc, with contributions from our community

* Where to get help:
Database Adminstrators (Stack Exchange), MariaDB Knowledge Base (Ask a
Question here).

Also see the "Getting Help with MariaDB" article on the MariaDB Knowledge Base.

SUPPORTED TAGS AND RESPECTIVE DOCKERFILE LINKS

* 11.4.1-rc-jammy, 11.4-rc-jammy, 11.4.1-rc, 11.4-rc
* 11.3.2-jammy, 11.3-jammy, 11-jammy, jammy, 11.3.2, 11.3, 11, latest
* 11.2.4-jammy, 11.2-jammy, 11.2.4, 11.2
* 11.1.5-jammy, 11.1-jammy, 11.1.5, 11.1
* 11.0.6-jammy, 11.0-jammy, 11.0.6, 11.0
* 10.11.8-jammy, 10.11-jammy, 10-jammy, lts-jammy, 10.11.8, 10.11, 10, lts
* 10.6.18-focal, 10.6-focal, 10.6.18, 10.6
* 10.5.25-focal, 10.5-focal, 10.5.25, 10.5
* 10.4.34-focal, 10.4-focal, 10.4.34, 10.4

QUICK REFERENCE (CONT.)

* Where to file issues:
Issues can be filed on https://jira.mariadb.org/ under the "MDEV" Project and
"Docker" Component, or on GitHub

* Supported architectures: (more info)
amd64, arm64v8, ppc64le, s390x

* Published image artifact details:
repo-info repo's repos/mariadb/ directory (history)
(image metadata, transfer size, etc)

* Image updates:
official-images repo's library/mariadb label
official-images repo's library/mariadb file (history)

* Source of this description:
docs repo's mariadb/ directory (history)

WHAT IS MARIADB?

MariaDB Server is one of the most popular database servers in the world. It's
made by the original developers of MySQL and guaranteed to stay open source.
Notable users include Wikipedia, DBS Bank, and ServiceNow.

The intent is also to maintain high compatibility with MySQL, ensuring a library
binary equivalency and exact matching with MySQL APIs and commands. MariaDB
developers continue to develop new features and improve performance to better
serve its users.

HOW TO USE THIS IMAGE

The mariadb has a number of tags, and of note is latest, as the latest stable
version, and lts, as the last long term support release.

RUNNING THE CONTAINER

STARTING USING A MINIMAL CONFIGURATION

The environment variables required to use this image involves the setting of the
root user password:

$ docker run --detach --name some-mariadb --env MARIADB_ROOT_PASSWORD=my-secret-pw mariadb:latest

or:

$ docker run --detach --name some-mariadb --env MARIADB_ALLOW_EMPTY_ROOT_PASSWORD=1 mariadb:latest

or:

$ docker run --detach --name some-mariadb --env MARIADB_RANDOM_ROOT_PASSWORD=1 mariadb:latest

... where the container logs will contain the generated root password.

... VIA DOCKER-COMPOSE OR DOCKER STACK DEPLOY

Example docker-compose.yml for mariadb:

# Use root/example as user/password credentials
version: '3.1'

services:

db:
image: mariadb
restart: always
environment:
MARIADB_ROOT_PASSWORD: example

adminer:
image: adminer
restart: always
ports:
- 8080:8080

Run docker stack deploy -c stack.yml mariadb (or docker-compose -f stack.yml
up), wait for it to initialize completely, and visit http://swarm-ip:8080,
http://localhost:8080, or http://host-ip:8080 (as appropriate).

START A MARIADB SERVER INSTANCE WITH USER, PASSWORD AND DATABASE

Starting a MariaDB instance with a user, password, and a database:

$ docker run --detach --name some-mariadb --env MARIADB_USER=example-user --env MARIADB_PASSWORD=my_cool_secret --env MARIADB_DATABASE=exmple-database --env MARIADB_ROOT_PASSWORD=my-secret-pw mariadb:latest

START A MARIADB SERVER INSTANCE IN A NETWORK

As applications talk to MariaDB, MariaDB needs to start in the same network as
the application:

$ docker network create some-network
$ docker run --detach --network some-network --name some-mariadb --env MARIADB_USER=example-user --env MARIADB_PASSWORD=my_cool_secret --env MARIADB_ROOT_PASSWORD=my-secret-pw mariadb:latest
$ docker run --detach --network some-network --name some-application --env APP_DB_HOST=some-mariadb --env APP_DB_USER=example-user --env APP_DB_PASSWD=my_cool_secret some-application

... where some-network is a newly created network (other than bridge as the
default network), some-mariadb is the name you want to assign to your container,
my-secret-pw is the password to be set for the MariaDB root user. See the list
above for relevant tags to match your needs and environment. some-application
and then environment variable APP_DB_HOST, APP_DB_USER and APP_DB_PASSWD are the
application's configuration for its database connection.

CONNECT TO MARIADB FROM THE MARIADB COMMAND LINE CLIENT

The following command starts another mariadb container instance and runs the
mariadb command line client against your original mariadb container, allowing
you to execute SQL statements against your database instance:

$ docker run -it --network some-network --rm mariadb mariadb -hsome-mariadb -uexample-user -p

... where some-mariadb is the name of your original mariadb container (connected
to the some-network Docker network).

This image can also be used as a client for non-Docker or remote instances:

$ docker run -it --rm mariadb mariadb --host <server container IP> --user example-user --password --database test

That will give you a standard MariaDB prompt. You can test it with:

MariaDB [(none)]> \s
--------------
client/mariadb Ver 15.1 Distrib 10.6.16-MariaDB, for Linux (x86_64) using EditLine wrapper

Connection id: 20
Current database: test
Current user: example-user@bark
SSL: Not in use
Current pager: stdout
Using outfile: ''
Using delimiter: ;
Server: MariaDB
Server version: 10.6.16-MariaDB Source distribution
Protocol version: 10
Connection: 192.168.178.73 via TCP/IP
Server characterset: latin1
Db characterset: latin1
Client characterset: utf8mb3
Conn. characterset: utf8mb3
TCP port: 3306
Uptime: 6 min 4 sec

Threads: 1 Questions: 32 Slow queries: 0 Opens: 20 Open tables: 13 Queries per second avg: 0.087
--------------

... which will give you the version and connection information. You can then use
exit to leave the MariaDB command line client and the client container.

More information about the MariaDB command-line client can be found in the
MariaDB Knowledge Base : MariaDB Command Line Client.

CONTAINER SHELL ACCESS

The docker exec command allows you to run commands inside the running container.
The following command line will give you a bash shell inside your mariadb
container:

$ docker exec -it some-mariadb bash

MARIADB-BACKUP

As MariaDB-Backup is highly coupled with the server version, it can be useful to
use the mariadb-backup in the mariadb container of an explicit version:

$ docker run --volume /backup-volume:/backup --rm mariadb:10.6.15 mariadb-backup --help

CONTAINER VIEWING MARIADB LOGS

The log is available through Docker's container log:

$ docker logs some-mariadb

USING A CUSTOM MARIADB CONFIGURATION FILE

Custom configuration files should end in .cnf and be mounted read only at the
directory /etc/mysql/conf.d. These files should contain the minimal changes from
the MariaDB workload required for your application/environment. A MariaDB
configuration file will have a [mariadb] group followed by variable = value
settings per Setting Server System Variables or option-prefix-variable.

The mariadb image configuration contains the Ubuntu MariaDB variables with two
custom changes for the container:

[host-cache-size=0](https://mariadb.com/kb/en/server-system-variables/#host_cache_size)
[skip-name-resolve](https://mariadb.com/kb/en/server-system-variables/#skip_name_resolve)

These disable the authentication of user@hostname users. To re-enable the
skip-name-resolve use disable-skip-name-resolve as variable or argument. When
enabled, the host-cache-size should be sufficient for the number of containers
connecting to the mariadb.

To view the resulting configuration of your mariadb container:

$ docker run --name some-mariadb -v /my/custom:/etc/mysql/conf.d --rm mariadb:latest my_print_defaults --mysqld

CONFIGURATION WITHOUT A CNF FILE

Many configuration options can be passed as flags to mariadbd. This will give
you the flexibility to customize the container without needing a cnf file. For
example, if you want to run on port 3808 just run the following:

$ docker run --name some-mariadb -e MARIADB_ROOT_PASSWORD=my-secret-pw -d mariadb:latest --port 3808

If you would like to see a complete list of available options, just run:

$ docker run -it --rm mariadb:latest --verbose --help

ENVIRONMENT VARIABLES

When you start the mariadb image, you can adjust the initialization of the
MariaDB instance by passing one or more environment variables on the docker run
command line. Do note that all of the variables, except MARIADB_AUTO_UPGRADE,
will have no effect if you start the container with a data directory that
already contains a database. I.e. any pre-existing database will always be left
untouched on container startup.

One of MARIADB_RANDOM_ROOT_PASSWORD, MARIADB_ROOT_PASSWORD_HASH,
MARIADB_ROOT_PASSWORD or MARIADB_ALLOW_EMPTY_ROOT_PASSWORD (or equivalents,
including *_FILE), is required. The other environment variables are optional.

There is a large list of environment variables and the complete list is
documented on MariaDB's Knowledge Base : MariaDB Server Docker Official Image
Environment Variables.

MARIADB_AUTO_UPGRADE

When this environment variable is set, this will run the mariadb-upgrade, if
needed, so any changes in the MariaDB system tables required to expose new
features will be made. This may impeed some downgrade options. Unless the
environment variable MARIADB_DISABLE_UPGRADE_BACKUP is set, there will be a
backup of the system tables created as system_mysql_backup_*.sql.zst in the top
level of the data directory to assist in the downgrade if needed.

SECRETS

As an alternative to passing sensitive information via environment variables,
_FILE may be appended to the previously listed environment variables, causing
the initialization script to load the values for those variables from files
present in the container. In particular, this can be used to load passwords from
Docker secrets stored in /run/secrets/<secret_name> files. For example:

$ docker run --name some-mysql -e MARIADB_ROOT_PASSWORD_FILE=/run/secrets/mariadb-root -d mariadb:latest

INITIALIZING THE DATABASE CONTENTS

When a container is started for the first time, a new database with the
specified name will be created and initialized with the provided configuration
variables. Furthermore, it will execute files with extensions .sh, .sql,
.sql.gz, .sql.xz and .sql.zst that are found in /docker-entrypoint-initdb.d.
Files will be executed in alphabetical order. .sh files without file execute
permission are sourced rather than executed. You can easily populate your
mariadb services by mounting a SQL dump into that directory and provide custom
images with contributed data. SQL files will be imported by default to the
database specified by the MARIADB_DATABASE variable.

CAVEATS

WHERE TO STORE DATA

Important note: There are several ways to store data used by applications that
run in Docker containers. We encourage users of the mariadb images to
familiarize themselves with the options available, including:

* Use a named volume using the container manager to manage the storage of your
database data by writing the database files to disk on the host system using
its own internal volume management. This is the default and is easy and
fairly transparent to the user. The downside is that the files may be hard to
locate for tools and applications that run directly on the host system, i.e.
outside containers.
* Create a data directory on the host system (outside the container) and mount
this to a directory visible from inside the container. This places the
database files in a known location on the host system, and makes it easy for
tools and applications on the host system to access the files. The downside
is that the user needs to make sure that the directory exists, and that e.g.
directory permissions and other security mechanisms on the host system are
set up correctly.

The Docker documentation is a good starting point for understanding the
different storage options and variations, and there are multiple blogs and forum
postings that discuss and give advice in this area. We will simply show the
basic procedure here for the latter option above:

1. Create a data directory on a suitable volume on your host system, e.g.
/my/own/datadir.

2. Start your mariadb container like this:

$ docker run --name some-mariadb -v /my/own/datadir:/var/lib/mysql:Z -e MARIADB_ROOT_PASSWORD=my-secret-pw -d mariadb:latest

The -v /my/own/datadir:/var/lib/mysql:Z part of the command mounts the
/my/own/datadir directory from the underlying host system as /var/lib/mysql
inside the container, where MariaDB by default will write its data files.

NO CONNECTIONS UNTIL MARIADB INIT COMPLETES

If there is no database initialized when the container starts, then a default
database will be created. While this is the expected behavior, this means that
it will not accept incoming connections until such initialization completes.
This may cause issues when using automation tools, such as docker-compose, which
start several containers simultaneously.

HEALTH/LIVENESS/READINESS CHECKING

See the "Official Images" FAQ for why there is no default HEALTHCHECK directive.
However, you can use the healthcheck.sh script to choose from a (non-exhaustive)
list of tests to check for whatever you consider health/liveness/readiness.
Refer to the MariaDB Knowledge Base : Using Healthcheck.sh to learn about how to
use it and which exact tests are provided.

USAGE AGAINST AN EXISTING DATABASE

If you start your mariadb container instance with a data directory that already
contains a database (specifically, a mysql subdirectory), no environment
variables that control initialization will be needed or examined, and no
pre-existing databases will be changed. The only exception is the non-default
MARIADB_AUTO_UPGRADE environment variable, that might cause
mysql_upgrade/mariadb-upgrade to run, which might change the system tables.

BACKUPS AND RESTORES

Backing up and restoring databases is important in containers too. The
documentation on how to do this can be found on the MariaDB Knowledge Base :
Container Backup and Restoration.

FREQUENTLY ASKED QUESTIONS / HOW TO RESET ROOT AND USER PASSWORDS

This is documented on MariaDB Knowledge Base : Frequenty Asked Questions of
Docker Official Image.

HOW TO INSTALL MARIADB PLUGINS

This is documented on MariaDB Knowledge Base : Adding Plugins to the Docker
Official Image.

RELATED IMAGES

* MariaDB MaxScale
* MariaDB ColumnStore

COMPOSE FILE EXAMPLES

Example compose files using this mariadb are located in
https://github.com/MariaDB/mariadb-docker in the /examples folder.

LICENSE

View license information for the software contained in this image.

As with all Docker images, these likely also contain other software which may be
under other licenses (such as Bash, etc from the base distribution, along with
any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be
found in the repo-info repository's mariadb/ directory.

As for any pre-built image usage, it is the image user's responsibility to
ensure that any use of this image complies with any relevant licenses for all
software contained within.

RECENT TAGS

lts-jammy
lts
11.2.4-jammy
11.2.4
11.2-jammy
11.2
11.1.5-jammy
11.1.5
11.1-jammy
11.1

ABOUT OFFICIAL IMAGES

Docker Official Images are a curated set of Docker open source and drop-in
solution repositories.

WHY OFFICIAL IMAGES?

These images have clear documentation, promote best practices, and are designed
for the most common use cases.

WHY

OverviewWhat is a Container

PRODUCTS

Product Overview

PRODUCT OFFERINGS

Docker DesktopDocker Hub

FEATURES

Container RuntimeDeveloper ToolsDocker AppKubernetes

DEVELOPERS

Getting StartedPlay with DockerCommunityOpen SourceDocumentation

COMPANY

About UsResourcesBlogCustomersPartnersNewsroomEvents and WebinarsCareersContact
UsSystem Status⁠

--------------------------------------------------------------------------------

Back

Documentation
⁠
Forums
⁠
Contact Support
System Status
⁠

Back

Help

Docker Suite

Back

Documentation
⁠
Forums
⁠
Contact Support
System Status
⁠

Back

Admin Console
New
Manage users, control access, & set policies.

Docker Scout
New
Secure your supply chain at every level.

Docker Desktop
Local development, simplified.

Docker Build Cloud
New
Speed up your Docker Builds.

--------------------------------------------------------------------------------

Docs
Learn how to use Docker.

Community Forums
Get help from the community.

System Status
Check the status of Docker services.

By clicking “Accept All Cookies”, you agree to the storing of cookies on your
device to enhance site navigation, analyze site usage, and assist in our
marketing efforts.
Cookies Settings Reject All Accept All Cookies

PRIVACY PREFERENCE CENTER

When you visit any website, it may store or retrieve information on your
browser, mostly in the form of cookies. This information might be about you,
your preferences or your device and is mostly used to make the site work as you
expect it to. The information does not usually directly identify you, but it can
give you a more personalized web experience. Because we respect your right to
privacy, you can choose not to allow some types of cookies. Click on the
different category headings to find out more and change our default settings.
However, blocking some types of cookies may impact your experience of the site
and the services we are able to offer.
More information
Allow All

MANAGE CONSENT PREFERENCES

FUNCTIONAL COOKIES

Functional Cookies

These cookies enable the website to provide enhanced functionality and
personalisation. They may be set by us or by third party providers whose
services we have added to our pages. If you do not allow these cookies then some
or all of these services may not function properly.

STRICTLY NECESSARY COOKIES

Always Active

These cookies are necessary for the website to function and cannot be switched
off in our systems. They are usually only set in response to actions made by you
which amount to a request for services, such as setting your privacy
preferences, logging in or filling in forms. You can set your browser to block
or alert you about these cookies, but some parts of the site will not then work.
These cookies do not store any personally identifiable information.

PERFORMANCE COOKIES

Performance Cookies

These cookies allow us to count visits and traffic sources so we can measure and
improve the performance of our site. They help us to know which pages are the
most and least popular and see how visitors move around the site. All
information these cookies collect is aggregated and therefore anonymous. If you
do not allow these cookies we will not know when you have visited our site, and
will not be able to monitor its performance.

TARGETING COOKIES

Targeting Cookies

These cookies may be set through our site by our advertising partners. They may
be used by those companies to build a profile of your interests and show you
relevant adverts on other sites. They do not store directly personal
information, but are based on uniquely identifying your browser and internet
device. If you do not allow these cookies, you will experience less targeted
advertising.

Back Button

COOKIE LIST

Search Icon
Filter Icon

Clear
checkbox label label
Apply Cancel
Consent Leg.Interest
checkbox label label
checkbox label label
checkbox label label

Reject All Confirm My Choices

hub.docker.com Open in urlscan Pro 2600:1f18:2148:bc02:a090:6a5b:b2ff:3152 Public Scan

Form analysis 1 forms found in the DOM

GET /search

Text Content

hub.docker.com Open in urlscan Pro
2600:1f18:2148:bc02:a090:6a5b:b2ff:3152 Public Scan

Form analysis
1 forms found in the DOM