MariaDB is a community-developed fork of the MySQL relational database management system intended to remain free under the GNU GPL. Being a fork of a leading open source software system, it is notable for being led by the original developers of MySQL, who forked it due to concerns over its acquisition by Oracle. Contributors are required to share their copyright with the MariaDB Foundation.
Learn more about MariaDB: https://mariadb.org/
This Docker container makes it easy to get an instance of MariaDB up and running.
Based on Official Ubuntu Docker Image with some minor hack:
- Packaging by Packer Docker builder and Ansible provisioner in single layer
- Handle
ENTRYPOINTwith catatonit - Use Kubernetes Peer Finder to start the actual database instance with auto peer discovery
For the VOLUME directory that is used to store the repository data
(amongst other things) we recommend mounting a host directory as a data
volume,
or via a named volume if using a docker version >= 1.9.
Start MariaDB:
# Pull latest image
docker pull alvistack/mariadb-11.4
# Run as detach
docker run \
-itd \
--name mariadb \
--publish 3306:3306 \
--volume /var/lib/mysql:/var/lib/mysql \
--env MYSQL_ROOT_PASSWORD=Passw0rd\! \
alvistack/mariadb-11.4
Success. MariaDB is now available on port 3306.
Be sure to use the
service.alpha.kubernetes.io/tolerate-unready-endpoints on the
governing headless service of the StatefulSet so that all peers are
listed in endpoints before any peers are started, e.g.
---
apiVersion: v1
kind: Service
metadata:
name: mariadb
annotations:
service.alpha.kubernetes.io/tolerate-unready-endpoints: "true"
labels:
service: mariadb
spec:
ports:
- name: mysql
port: 3306
- name: state-snapshot-transfer
port: 4444
- name: replication-traffic
port: 4567
- name: incremental-state-transfer
port: 4568
selector:
service: mariadb
clusterIP: None
Also need to use peer-finder as wrapper in order to start daemon with
peer auto discovery, e.g.
...
containers:
- name: mariadb
image: alvistack/mariadb-11.4:latest
imagePullPolicy: Always
ports:
- containerPort: 3306
- containerPort: 4444
- containerPort: 4567
- containerPort: 4568
env:
- name: MYSQL_DATABASE
value: "default"
- name: MYSQL_ROOT_PASSWORD
valueFrom:
secretKeyRef:
name: mariadb
key: MYSQL_ROOT_PASSWORD
- name: POD_NAMESPACE
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.namespace
args:
- /bin/sh
- -c
- peer-finder -on-start=on-start.sh -service=mariadb
...
Checkout our Kubernetes StatefulSet Example for more information.
In case of rolling upgrade or reboot which usually only single MariaDB instance goes offline, once it resumed no manual interrupt is required for automatic cluster recovery.
In case of unclean shutdown or hard crash, all nodes will have
safe_to_bootstrap: 0 therefore the automatic cluster recovery will be
failed. You may simply delete ALL running MariaDB pods (which should
already in CrashLoopBackOff status) so StatefulSet will help you
bootstrap a new cluster one-node-by-one-node.
Here we take a simple assumption that your 1st pod, i.e.
mariadb-0, has committed the last transaction in the cluster, therefore bootstrap a new cluster from it. This will only be truth if ALL pods are unclean shutdown or hard crash TOGETHER, e.g. during data center power shortage. If you hope to ensure none of data loss during recovery, checkout official documents for more information.
Refer to Official MariaDB Docker Image for more information. Additionally:
The namespace this pod is running in, used by peer-finder when running
as Kubernetes StatefulSet.
Default: default
Release tags could be find from GitHub Release of this repository. Thus using these tags will ensure you are running the most up to date stable version of this image.
Version tags ended with .0.0 are rolling release rebuild by GitLab
pipeline in
weekly basis. Thus using these tags will ensure you are running the
latest packages provided by the base image project.
- Code released under Apache License 2.0
- Docs released under CC BY 4.0
- Wong Hoi Sing Edison