bitnami/mariadb
Bitnami container image for MariaDB
500M+
MariaDB is an open source, community-developed SQL database server that is widely in use around the world due to its enterprise features, flexibility, and collaboration with leading tech firms.
Overview of MariaDB Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
docker run --name mariadb -e ALLOW_EMPTY_PASSWORD=yes bitnami/mariadb:latest
Warning: These quick setups are only intended for development environments. You are encouraged to change the insecure default credentials and check out the available configuration options in the Configuration section for a more secure deployment.
Looking to use MariaDB in production? Try VMware Tanzu Application Catalog, the commercial edition of the Bitnami catalog.
Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami MariaDB Chart GitHub repository.
Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.
Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers in our docs.
Starting December 10th 2024, only the latest stable branch of any container will receive updates in the free Bitnami catalog. To access up-to-date releases for all upstream-supported branches, consider upgrading to Bitnami Premium. Previous versions already released will not be deleted. They are still available to pull from DockerHub.
Please check the Bitnami Premium page in our partner Arrow Electronics for more information.
Dockerfile
linksLearn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.
You can see the equivalence between the different tags by taking a look at the tags-info.yaml
file present in the branch folder, i.e bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml
.
Subscribe to project updates by watching the bitnami/containers GitHub repo.
The recommended way to get the Bitnami MariaDB Docker Image is to pull the prebuilt image from the Docker Hub Registry.
docker pull bitnami/mariadb:latest
To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.
docker pull bitnami/mariadb:[TAG]
If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the docker build
command. Remember to replace the APP
, VERSION
and OPERATING-SYSTEM
path placeholders in the example command below with the correct values.
git clone https://github.com/bitnami/containers.git
cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .
If you remove the container all your data will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
For persistence you should mount a directory at the /bitnami/mariadb
path. If the mounted directory is empty, it will be initialized on the first run.
docker run \
-e ALLOW_EMPTY_PASSWORD=yes \
-v /path/to/mariadb-persistence:/bitnami/mariadb \
bitnami/mariadb:latest
or by modifying the docker-compose.yml
file present in this repository:
services:
mariadb:
...
volumes:
- /path/to/mariadb-persistence:/bitnami/mariadb
...
NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID
1001
.
Using Docker container networking, a MariaDB server running inside a container can easily be accessed by your application containers.
Containers attached to the same network can communicate with each other using the container name as the hostname.
In this example, we will create a MariaDB client instance that will connect to the server instance that is running on the same docker network as the client.
Step 1: Create a network
docker network create app-tier --driver bridge
Step 2: Launch the MariaDB server instance
Use the --network app-tier
argument to the docker run
command to attach the MariaDB container to the app-tier
network.
docker run -d --name mariadb-server \
-e ALLOW_EMPTY_PASSWORD=yes \
--network app-tier \
bitnami/mariadb:latest
Step 3: Launch your MariaDB client instance
Finally we create a new container instance to launch the MariaDB client and connect to the server created in the previous step:
docker run -it --rm \
--network app-tier \
bitnami/mariadb:latest mysql -h mariadb-server -u root
When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new bridge
network named app-tier
. In this example we assume that you want to connect to the MariaDB server from your own custom application image which is identified in the following snippet by the service name myapp
.
version: '2'
networks:
app-tier:
driver: bridge
services:
mariadb:
image: 'bitnami/mariadb:latest'
environment:
- ALLOW_EMPTY_PASSWORD=yes
networks:
- app-tier
myapp:
image: 'YOUR_APPLICATION_IMAGE'
networks:
- app-tier
IMPORTANT:
- Please update the
YOUR_APPLICATION_IMAGE
placeholder in the above snippet with your application image- In your application container, use the hostname
mariadb
to connect to the MariaDB server
Launch the containers using:
docker-compose up -d
Customizable environment variables
Name | Description | Default Value |
---|---|---|
ALLOW_EMPTY_PASSWORD | Allow MariaDB access without any password. | no |
MARIADB_AUTHENTICATION_PLUGIN | MariaDB authentication plugin to configure during the first initialization. | nil |
MARIADB_ROOT_USER | MariaDB database root user. | root |
MARIADB_ROOT_PASSWORD | MariaDB database root user password. | nil |
MARIADB_USER | MariaDB database user to create during the first initialization. | nil |
MARIADB_PASSWORD | Password for the MariaDB database user to create during the first initialization. | nil |
MARIADB_DATABASE | MariaDB database to create during the first initialization. | nil |
MARIADB_MASTER_HOST | Address for the MariaDB master node. | nil |
MARIADB_MASTER_PORT_NUMBER | Port number for the MariaDB master node. | 3306 |
MARIADB_MASTER_ROOT_USER | MariaDB database root user of the master host. | root |
MARIADB_MASTER_ROOT_PASSWORD | Password for the MariaDB database root user of the the master host. | nil |
MARIADB_MASTER_DELAY | MariaDB database replication delay. | 0 |
MARIADB_REPLICATION_USER | MariaDB replication database user. | nil |
MARIADB_REPLICATION_PASSWORD | Password for the MariaDB replication database user. | nil |
MARIADB_PORT_NUMBER | Port number to use for the MariaDB Server service. | nil |
MARIADB_REPLICATION_MODE | MariaDB replication mode. | nil |
MARIADB_REPLICATION_SLAVE_DUMP | Make a dump on master and update slave MariaDB database | false |
MARIADB_EXTRA_FLAGS | Extra flags to be passed to start the MariaDB Server. | nil |
MARIADB_INIT_SLEEP_TIME | Sleep time when waiting for MariaDB init configuration operations to finish. | nil |
MARIADB_CHARACTER_SET | MariaDB collation to use. | nil |
MARIADB_COLLATE | MariaDB collation to use. | nil |
MARIADB_BIND_ADDRESS | MariaDB bind address. | nil |
MARIADB_SQL_MODE | MariaDB Server SQL modes to enable. | nil |
MARIADB_UPGRADE | MariaDB upgrade option. | AUTO |
MARIADB_SKIP_TEST_DB | Whether to skip creating the test database. | no |
MARIADB_CLIENT_ENABLE_SSL | Whether to force SSL for connections to the MariaDB database. | no |
MARIADB_CLIENT_SSL_CA_FILE | Path to CA certificate to use for SSL connections to the MariaDB database server. | nil |
MARIADB_CLIENT_SSL_CERT_FILE | Path to client public key certificate to use for SSL connections to the MariaDB database server. | nil |
MARIADB_CLIENT_SSL_KEY_FILE | Path to client private key to use for SSL connections to the MariaDB database server. | nil |
MARIADB_CLIENT_EXTRA_FLAGS | Whether to force SSL connections with the "mysql" CLI tool. Useful for applications that rely on the CLI instead of APIs. | no |
MARIADB_STARTUP_WAIT_RETRIES | Number of retries waiting for the database to be running. | 300 |
MARIADB_STARTUP_WAIT_SLEEP_TIME | Sleep time between retries waiting for the database to be running. | 2 |
MARIADB_ENABLE_SLOW_QUERY | Whether to enable slow query logs. | 0 |
MARIADB_LONG_QUERY_TIME | How much time, in seconds, defines a slow query. | 10.0 |
Read-only environment variables
Name | Description | Value |
---|---|---|
DB_FLAVOR | SQL database flavor. Valid values: mariadb or mysql . | mariadb |
DB_BASE_DIR | Base path for MariaDB files. | ${BITNAMI_ROOT_DIR}/mariadb |
DB_VOLUME_DIR | MariaDB directory for persisted files. | ${BITNAMI_VOLUME_DIR}/mariadb |
DB_DATA_DIR | MariaDB directory for data files. | ${DB_VOLUME_DIR}/data |
DB_BIN_DIR | MariaDB directory where executable binary files are located. | ${DB_BASE_DIR}/bin |
DB_SBIN_DIR | MariaDB directory where service binary files are located. | ${DB_BASE_DIR}/sbin |
DB_CONF_DIR | MariaDB configuration directory. | ${DB_BASE_DIR}/conf |
DB_DEFAULT_CONF_DIR | MariaDB default configuration directory. | ${DB_BASE_DIR}/conf.default |
DB_LOGS_DIR | MariaDB logs directory. | ${DB_BASE_DIR}/logs |
DB_TMP_DIR | MariaDB directory for temporary files. | ${DB_BASE_DIR}/tmp |
DB_CONF_FILE | Main MariaDB configuration file. | ${DB_CONF_DIR}/my.cnf |
DB_PID_FILE | MariaDB PID file. | ${DB_TMP_DIR}/mysqld.pid |
DB_SOCKET_FILE | MariaDB Server socket file. | ${DB_TMP_DIR}/mysql.sock |
DB_DAEMON_USER | Users that will execute the MariaDB Server process. | mysql |
DB_DAEMON_GROUP | Group that will execute the MariaDB Server process. | mysql |
MARIADB_DEFAULT_PORT_NUMBER | Default port number to use for the MariaDB Server service. | 3306 |
MARIADB_DEFAULT_CHARACTER_SET | Default MariaDB character set. | utf8mb4 |
MARIADB_DEFAULT_BIND_ADDRESS | Default MariaDB bind address. | 0.0.0.0 |
When the container is executed for the first time, it will execute the files with extensions .sh
, .sql
and .sql.gz
located at /docker-entrypoint-startdb.d
.
In order to have your custom files inside the docker image you can mount them as a volume.
Take into account those scripts are treated differently depending on the extension. While the .sh
scripts are executed in all the nodes; the .sql
and .sql.gz
scripts are only executed in the master nodes. The reason behind this differentiation is that the .sh
scripts allow adding conditions to determine what is the node running the script, while these conditions can't be set using .sql
nor sql.gz
files. This way it is possible to cover different use cases depending on their needs.
NOTE: If you are importing large databases, it is recommended to import them as
.sql
instead of.sql.gz
, as the latter one needs to be decompressed on the fly and not allowing for additional optimizations to import large files.
Passing extra command-line flags to the mysqld service command is possible through the following env var:
MARIADB_EXTRA_FLAGS
: Flags to be appended to the startup command. No defaultsdocker run --name mariadb -e ALLOW_EMPTY_PASSWORD=yes -e MARIADB_EXTRA_FLAGS='--max-connect-errors=1000 --max_connections=155' bitnami/mariadb:latest
or by modifying the docker-compose.yml
file present in this repository:
services:
mariadb:
...
environment:
- ALLOW_EMPTY_PASSWORD=yes
- MARIADB_EXTRA_FLAGS=--max-connect-errors=1000 --max_connections=155
...
It is possible to configure the character set and collation used by default by the database with the following environment variables:
MARIADB_CHARACTER_SET
: The default character set to use. Default: utf8
MARIADB_COLLATE
: The default collation to use. Default: utf8_general_ci
The root user and password can easily be setup with the Bitnami MariaDB Docker image using the following environment variables:
MARIADB_ROOT_USER
: The database admin user. Defaults to root
.MARIADB_ROOT_PASSWORD
: The database admin user password. No defaults.MARIADB_ROOT_PASSWORD_FILE
: Path to a file that contains the admin user password. This will override the value specified in MARIADB_ROOT_PASSWORD
. No defaults.Passing the MARIADB_ROOT_PASSWORD
environment variable when running the image for the first time will set the password of the MARIADB_ROOT_USER
user to the value of MARIADB_ROOT_PASSWORD
.
docker run --name mariadb -e MARIADB_ROOT_PASSWORD=password123 bitnami/mariadb:latest
or by modifying the docker-compose.yml
file present in this repository:
services:
mariadb:
...
environment:
- MARIADB_ROOT_PASSWORD=password123
...
Warning The MARIADB_ROOT_USER
user is always created with remote access. It's suggested that the MARIADB_ROOT_PASSWORD
env variable is always specified to set a password for the MARIADB_ROOT_USER
user. In case you want to allow the MARIADB_ROOT_USER
user to access the database without a password set the environment variable ALLOW_EMPTY_PASSWORD=yes
. This is recommended only for development.
By default the MariaDB image expects all the available passwords to be set. In order to allow empty passwords, it is necessary to set the ALLOW_EMPTY_PASSWORD=yes
env variable. This env variable is only recommended for testing or development purposes. We strongly recommend specifying the MARIADB_ROOT_PASSWORD
for any other scenario.
docker run --name mariadb -e ALLOW_EMPTY_PASSWORD=yes bitnami/mariadb:latest
or by modifying the docker-compose.yml
file present in this repository:
services:
mariadb:
...
environment:
- ALLOW_EMPTY_PASSWORD=yes
...
By passing the MARIADB_DATABASE
environment variable when running the image for the first time, a database will be created. This is useful if your application requires that a database already exists, saving you from having to manually create the database using the MySQL client.
docker run --name mariadb \
-e ALLOW_EMPTY_PASSWORD=yes \
-e MARIADB_DATABASE=my_database \
bitnami/mariadb:latest
or by modifying the docker-compose.yml
file present in this repository:
services:
mariadb:
...
environment:
- ALLOW_EMPTY_PASSWORD=yes
- MARIADB_DATABASE=my_database
...
You can create a restricted database user that only has permissions for the database created with the MARIADB_DATABASE
environment variable. To do this, provide the MARIADB_USER
environment variable and to set a password for the database user provide the MARIADB_PASSWORD
variable (alternatively, you can set the MARIADB_PASSWORD_FILE
with the path to a file that contains the user password). MariaDB supports different authentication mechanisms, such as pam
or mysql_native_password
. To set it, use the MARIADB_AUTHENTICATION_PLUGIN
variable.
docker run --name mariadb \
-e ALLOW_EMPTY_PASSWORD=yes \
-e MARIADB_USER=my_user \
-e MARIADB_PASSWORD=my_password \
-e MARIADB_DATABASE=my_database \
bitnami/mariadb:latest
or by modifying the docker-compose.yml
file present in this repository:
services:
mariadb:
...
environment:
- ALLOW_EMPTY_PASSWORD=yes
- MARIADB_USER=my_user
- MARIADB_PASSWORD=my_password
- MARIADB_DATABASE=my_database
...
Note! The root
user will be created with remote access and without a password if ALLOW_EMPTY_PASSWORD
is enabled. Please provide the MARIADB_ROOT_PASSWORD
env variable instead if you want to set a password for the root
user.
By default MariaDB creates a test database. In order to disable the creation of this test database, the flag --skip-test-db
can be passed to mysql_install_db
. This function is only on MariaDB >= 10.5
.
To disable the test database in the Bitnami MariaDB container, set the MARIADB_SKIP_TEST_DB
environment variable to yes
during the first boot of the container.
docker run --name mariadb \
-e ALLOW_EMPTY_PASSWORD=yes \
-e MARIADB_SKIP_TEST_DB=yes \
bitnami/mariadb:latest
or by modifying the docker-compose.yml
file present in this repository:
services:
mariadb:
...
enviro
_Note: the README for this container is longer than the DockerHub length limit of 25000, so it has been trimmed. The full README can be found at https://github.com/bitnami/containers/blob/main/bitnami/mariadb/README.md_