MariaDB is a fast, reliable, scalable, and easy to use open-source relational database system. MariaDB Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.
docker run --name mariadb bitnami/mariadb:latest
version: '2'
services:
mariadb:
image: 'bitnami/mariadb:latest'
ports:
- '3306:3306'
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.
docker build -t bitnami/mariadb:latest https://github.com/bitnami/bitnami-docker-mariadb.git
If you remove the container all your data and configurations 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.
Note! If you have already started using your database, follow the steps on backing up and restoring to pull the data from your running container down to your host.
The image exposes a volume at /bitnami/mariadb
for the MariaDB data and configurations. For persistence you can mount a directory at this location from your host. If the mounted directory is empty, it will be initialized on the first run.
docker run -v /path/to/mariadb-persistence:/bitnami/mariadb bitnami/mariadb:latest
or using Docker Compose:
version: '2'
services:
mariadb:
image: 'bitnami/mariadb:latest'
ports:
- '3306:3306'
volumes:
- /path/to/mariadb-persistence:/bitnami/mariadb
If you want to connect to your MariaDB server inside another container, you can use the linking system provided by Docker.
The first step is to start our MariaDB server.
Docker's linking system uses container ids or names to reference containers. We can explicitly specify a name for our MariaDB server to make it easier to connect to other containers.
docker run --name mariadb bitnami/mariadb:latest
Now that we have our MariaDB server running, we can create another container that links to it by giving Docker the --link
option. This option takes the id or name of the container we want to link it to as well as a hostname to use inside the container, separated by a colon. For example, to have our MariaDB server accessible in another container with server
as it's hostname we would pass --link mariadb:server
to the Docker run command.
The Bitnami MariaDB Docker Image also ships with a MySQL client. To start the client, we can override the default command Docker runs by stating a different command to run after the image name.
docker run --rm -it --link mariadb:server bitnami/mariadb:latest mysql -h server -u root
We started the MySQL client passing in the -h
option that allows us to specify the hostname of the server, which we set to the hostname we created in the link.
Note! You can also run the MySQL client in the same container the server is running in using the Docker exec command.
docker exec -it mariadb mysql -u root
Copy the snippet below into your docker-compose.yml
to add MariaDB to your application.
services:
mariadb:
image: 'bitnami/mariadb:latest'
Update the definitions for containers you want to access your MariaDB server from to include a link to the mariadb
entry you added in Step 1.
services:
myapp:
image: 'myapp'
depends_on:
- mariadb
Inside myapp
, use mariadb
as the hostname for the MariaDB server.
Passing the MARIADB_ROOT_PASSWORD
environment variable when running the image for the first time will set the password of the root user to the value of MARIADB_ROOT_PASSWORD
.
docker run --name mariadb -e MARIADB_ROOT_PASSWORD=password123 bitnami/mariadb:latest
or using Docker Compose:
version: '2'
services:
mariadb:
image: 'bitnami/mariadb:latest'
ports:
- '3306:3306'
environment:
- MARIADB_ROOT_PASSWORD=password123
Warning The root
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 root
user.
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 MARIADB_DATABASE=my_database bitnami/mariadb:latest
or using Docker Compose:
version: '2'
services:
mariadb:
image: 'bitnami/mariadb:latest'
ports:
- '3306:3306'
environment:
- 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.
docker run --name mariadb \
-e MARIADB_USER=my_user -e MARIADB_PASSWORD=my_password \
-e MARIADB_DATABASE=my_database \
bitnami/mariadb:latest
or using Docker Compose:
version: '2'
services:
mariadb:
image: 'bitnami/mariadb:latest'
ports:
- '3306:3306'
environment:
- MARIADB_USER=my_user
- MARIADB_PASSWORD=my_password
- MARIADB_DATABASE=my_database
Note! The root
user will still be created with remote access. Please ensure that you have specified a password for the root
user using the MARIADB_ROOT_PASSWORD
env variable.
A zero downtime MariaDB master-slave replication cluster can easily be setup with the Bitnami MariaDB Docker image using the following environment variables:
MARIADB_REPLICATION_MODE
: The replication mode. Possible valuesmaster
/slave
. No defaults.MARIADB_REPLICATION_USER
: The replication user created on the master on first run. No defaults.MARIADB_REPLICATION_PASSWORD
: The replication users password. No defaults.MARIADB_MASTER_HOST
: Hostname/IP of replication master (slave parameter). No defaults.MARIABD_MASTER_PORT
: Server port of the replication master (slave parameter). Defaults to3306
.MARIADB_MASTER_USER
: User on replication master with access toMARIADB_DATABASE
(slave parameter). Defaults toroot
MARIADB_MASTER_PASSWORD
: Password of user on replication master with access toMARIADB_DATABASE
(slave parameter). No defaults.
In a replication cluster you can have one master and zero or more slaves. When replication is enabled the master node is in read-write mode, while the slaves are in read-only mode. For best performance its advisable to limit the reads to the slaves.
The first step is to start the MariaDB master.
docker run --name mariadb-master \
-e MARIADB_ROOT_PASSWORD=root_password \
-e MARIADB_REPLICATION_MODE=master \
-e MARIADB_REPLICATION_USER=my_repl_user \
-e MARIADB_REPLICATION_PASSWORD=my_repl_password \
-e MARIADB_USER=my_user \
-e MARIADB_PASSWORD=my_password \
-e MARIADB_DATABASE=my_database \
bitnami/mariadb:latest
In the above command the container is configured as the master
using the MARIADB_REPLICATION_MODE
parameter. A replication user is specified using the MARIADB_REPLICATION_USER
and MARIADB_REPLICATION_PASSWORD
parameters.
Next we start a MariaDB slave container.
docker run --name mariadb-slave --link mariadb-master:master \
-e MARIADB_ROOT_PASSWORD=root_password \
-e MARIADB_REPLICATION_MODE=slave \
-e MARIADB_REPLICATION_USER=my_repl_user \
-e MARIADB_REPLICATION_PASSWORD=my_repl_password \
-e MARIADB_MASTER_HOST=master \
-e MARIADB_MASTER_USER=my_user \
-e MARIADB_MASTER_PASSWORD=my_password \
-e MARIADB_USER=my_user \
-e MARIADB_PASSWORD=my_password \
-e MARIADB_DATABASE=my_database \
bitnami/mariadb:latest
In the above command the container is configured as a slave
using the MARIADB_REPLICATION_MODE
parameter. The MARIADB_MASTER_HOST
, MARIADB_MASTER_USER
and MARIADB_MASTER_PASSWORD
parameters are used by the slave to connect to the master and take a dump of the existing data in the database identified by MARIADB_DATABASE
. The replication user credentials are specified using the MARIADB_REPLICATION_USER
and MARIADB_REPLICATION_PASSWORD
parameters and should be the same as the one specified on the master.
Note! The cluster only replicates the database specified in the
MARIADB_DATABASE
parameter.
You now have a two node MariaDB master/slave replication cluster up and running. You can scale the cluster by adding/removing slaves without incurring any downtime.
With Docker Compose the master/slave replication can be setup using:
version: '2'
services:
mariadb-master:
image: 'bitnami/mariadb:latest'
ports:
- '3306'
volumes:
- /path/to/mariadb-persistence:/bitnami/mariadb
environment:
- MARIADB_REPLICATION_MODE=master
- MARIADB_REPLICATION_USER=repl_user
- MARIADB_REPLICATION_PASSWORD=repl_password
- MARIADB_ROOT_PASSWORD=root_password
- MARIADB_USER=my_user
- MARIADB_PASSWORD=my_password
- MARIADB_DATABASE=my_database
mariadb-slave:
image: 'bitnami/mariadb:latest'
ports:
- '3306'
depends_on:
- mariadb-master
environment:
- MARIADB_REPLICATION_MODE=slave
- MARIADB_REPLICATION_USER=repl_user
- MARIADB_REPLICATION_PASSWORD=repl_password
- MARIADB_MASTER_HOST=mariadb-master
- MARIADB_MASTER_PORT=3306
- MARIADB_MASTER_USER=my_user
- MARIADB_MASTER_PASSWORD=my_password
- MARIADB_ROOT_PASSWORD=root_password
- MARIADB_USER=my_user
- MARIADB_PASSWORD=my_password
- MARIADB_DATABASE=my_database
Scale the number of slaves using:
docker-compose scale mariadb-master=1 mariadb-slave=3
The above command scales up the number of slaves to 3
. You can scale down in the same manner.
Note: You should not scale up/down the number of master nodes. Always have only one master node running.
The image looks for configuration in the conf/
directory of /bitnami/mariadb
. As as mentioned in Persisting your database you can mount a volume at this location and copy your own configuration file in the conf/
directory as my_custom.cnf. That file will be included in the main configuration file and will overwrite any configuration you want to modify.
Run the MariaDB image, mounting a directory from your host.
docker run --name mariadb -v /path/to/mariadb-persistence:/bitnami/mariadb bitnami/mariadb:latest
or using Docker Compose:
version: '2'
services:
mariadb:
image: 'bitnami/mariadb:latest'
ports:
- '3306:3306'
volumes:
- /path/to/mariadb-persistence:/bitnami/mariadb
Edit the configuration on your host using your favorite editor.
vi /path/to/mariadb-persistence/conf/my.cnf
After changing the configuration, restart your MariaDB container for changes to take effect.
docker restart mariadb
or using Docker Compose:
docker-compose restart mariadb
Further Reading:
The Bitnami MariaDB Docker image sends the container logs to the stdout
. To view the logs:
docker logs mariadb
or using Docker Compose:
docker-compose logs mariadb
You can configure the containers logging driver using the --log-driver
option if you wish to consume the container logs differently. In the default configuration docker uses the json-file
driver.
To backup your data, configuration and logs, follow these simple steps:
docker stop mariadb
or using Docker Compose:
docker-compose stop mariadb
We need to mount two volumes in a container we will use to create the backup: a directory on your host to store the backup in, and the volumes from the container we just stopped so we can access the data.
docker run --rm -v /path/to/mariadb-backups:/backups --volumes-from mariadb busybox \
cp -a /bitnami/mariadb:latest /backups/latest
or using Docker Compose:
docker run --rm -v /path/to/mariadb-backups:/backups --volumes-from `docker-compose ps -q mariadb` busybox \
cp -a /bitnami/mariadb:latest /backups/latest
Restoring a backup is as simple as mounting the backup as volumes in the container.
docker run -v /path/to/mariadb-backups/latest:/bitnami/mariadb bitnami/mariadb:latest
or using Docker Compose:
version: '2'
services:
mariadb:
image: 'bitnami/mariadb:latest'
ports:
- '3306:3306'
volumes:
- /path/to/mariadb-backups/latest:/bitnami/mariadb
Bitnami provides up-to-date versions of MariaDB, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.
docker pull bitnami/mariadb:latest
or if you're using Docker Compose, update the value of the image property to
bitnami/mariadb:latest
.
Before continuing, you should backup your container's data, configuration and logs.
Follow the steps on creating a backup.
docker rm -v mariadb
or using Docker Compose:
docker-compose rm -v mariadb
Re-create your container from the new image, restoring your backup if necessary.
docker run --name mariadb bitnami/mariadb:latest
or using Docker Compose:
docker-compose start mariadb
This image is tested for expected runtime behavior, using the Bats testing framework. You can run the tests on your machine using the bats
command.
bats test.sh
- All volumes have been merged at
/bitnami/mariadb
. Now you only need to mount a single volume at/bitnami/mariadb
for persistence. - The logs are always sent to the
stdout
and are no longer collected in the volume.
We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.
If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:
- Host OS and version
- Docker version (
docker version
) - Output of
docker info
- Version of this container (
echo $BITNAMI_IMAGE_VERSION
inside the container) - The command you used to run the container, and any relevant output you saw (masking any sensitive information)
Copyright (c) 2015-2016 Bitnami
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.