Portainer Templates logo

Portainer Templates

MariaDB Galera MariaDB Galera

Stack

Databases

3-node MariaDB 11.8 LTS cluster with Galera synchronous multi-primary replication - every node accepts writes, any node can die. Runs the OFFICIAL mariadb image (the Galera library ships in it); clustering is pure command-line flags.

Configuration

Type
Compose
Platform
linux
Env vars
MARIADB_APP_PASSWORD=''MARIADB_ROOT_PASSWORD=''
Source
Repo

Template by deployable-sh·Source

Report issue

Services

galera-1

Configuration

Command
mariadbd,--wsrep_on=ON,--wsrep_provider=/usr/lib/galera/libgalera_smm.so,--wsrep_cluster_name=galera,--wsrep_cluster_address=gcomm://galera-1,galera-2,galera-3,--wsrep_node_name=galera-1,--binlog_format=ROW,--innodb_autoinc_lock_mode=2
Volumes
/var/lib/mysql : galeradata-1
Env vars
MARIADB_ROOT_PASSWORD=${MARIADB_ROOT_PASSWORD}MARIADB_DATABASE=appMARIADB_USER=appMARIADB_PASSWORD=${MARIADB_APP_PASSWORD}
Restart
unless-stopped
Build
./bootstrap

galera-2

Configuration

Image
mariadb:11.8
Command
mariadbd,--wsrep_on=ON,--wsrep_provider=/usr/lib/galera/libgalera_smm.so,--wsrep_cluster_name=galera,--wsrep_cluster_address=gcomm://galera-1,galera-2,galera-3,--wsrep_node_name=galera-2,--binlog_format=ROW,--innodb_autoinc_lock_mode=2
Volumes
/var/lib/mysql : galeradata-2
Env vars
MARIADB_ROOT_PASSWORD=${MARIADB_ROOT_PASSWORD}
Restart
unless-stopped

Image details

Pulls: 3.2B
User: stackbrew
Created: Nov 25, 2014
Updated: 1 day ago
Status: active

galera-3

Configuration

Image
mariadb:11.8
Command
mariadbd,--wsrep_on=ON,--wsrep_provider=/usr/lib/galera/libgalera_smm.so,--wsrep_cluster_name=galera,--wsrep_cluster_address=gcomm://galera-1,galera-2,galera-3,--wsrep_node_name=galera-3,--binlog_format=ROW,--innodb_autoinc_lock_mode=2
Volumes
/var/lib/mysql : galeradata-3
Env vars
MARIADB_ROOT_PASSWORD=${MARIADB_ROOT_PASSWORD}
Restart
unless-stopped

Image details

Pulls: 3.2B
User: stackbrew
Created: Nov 25, 2014
Updated: 1 day ago
Status: active

Standalone Install

Select an install method, to see config/commands for deploying MariaDB Galera

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select MariaDB Galera, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

name: mariadb-galera

x-galera-env: &galera-env
  MARIADB_ROOT_PASSWORD: ${MARIADB_ROOT_PASSWORD}

x-galera-common: &galera-common
  restart: unless-stopped
  stop_grace_period: 2m
  healthcheck:
    test: ["CMD", "healthcheck.sh", "--connect", "--galera_online"]
    interval: 10s
    timeout: 5s
    retries: 12
    start_period: 90s

services:
  galera-1:
    <<: *galera-common
    build: ./bootstrap
    command:
      - mariadbd
      - --wsrep_on=ON
      - --wsrep_provider=/usr/lib/galera/libgalera_smm.so
      - --wsrep_cluster_name=galera
      - --wsrep_cluster_address=gcomm://galera-1,galera-2,galera-3
      - --wsrep_node_name=galera-1
      - --binlog_format=ROW
      - --innodb_autoinc_lock_mode=2
    environment:
      <<: *galera-env
      MARIADB_DATABASE: app
      MARIADB_USER: app
      MARIADB_PASSWORD: ${MARIADB_APP_PASSWORD}
    volumes:
      - galeradata-1:/var/lib/mysql

  galera-2:
    <<: *galera-common
    image: mariadb:11.8
    command:
      - mariadbd
      - --wsrep_on=ON
      - --wsrep_provider=/usr/lib/galera/libgalera_smm.so
      - --wsrep_cluster_name=galera
      - --wsrep_cluster_address=gcomm://galera-1,galera-2,galera-3
      - --wsrep_node_name=galera-2
      - --binlog_format=ROW
      - --innodb_autoinc_lock_mode=2
    environment: *galera-env
    volumes:
      - galeradata-2:/var/lib/mysql

  galera-3:
    <<: *galera-common
    image: mariadb:11.8
    command:
      - mariadbd
      - --wsrep_on=ON
      - --wsrep_provider=/usr/lib/galera/libgalera_smm.so
      - --wsrep_cluster_name=galera
      - --wsrep_cluster_address=gcomm://galera-1,galera-2,galera-3
      - --wsrep_node_name=galera-3
      - --binlog_format=ROW
      - --innodb_autoinc_lock_mode=2
    environment: *galera-env
    volumes:
      - galeradata-3:/var/lib/mysql

volumes:
  galeradata-1:
  galeradata-2:
  galeradata-3:

Or deploy it directly from the source:

git clone https://github.com/deployable-sh/stacks
cd stacks
docker compose -f mariadb-galera/compose.yaml up -d

More install options in our documentation.

Container Documentation

galera-2 Documentation

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

galera-3 Documentation

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

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Image won't pull

Test the pull directly on the host: docker pull mariadb:11.8

  • "manifest unknown" means the tag no longer exists.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

MariaDB Galera is a Compose stack, a set of containers (3 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.

The services

This stack is built from 3 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:

  • galera-1
  • galera-2 runs mariadb:11.8
  • galera-3 runs mariadb:11.8

Volumes

A volume is where MariaDB Galera keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /var/lib/mysql kept in the galeradata-1 volume Docker manages
  • /var/lib/mysql kept in the galeradata-2 volume Docker manages
  • /var/lib/mysql kept in the galeradata-3 volume Docker manages

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. MariaDB Galera takes 4 of them, all with defaults you can leave alone or tweak:

  • MARIADB_ROOT_PASSWORD, pulled from your own environment
  • MARIADB_DATABASE, defaults to app
  • MARIADB_USER, defaults to app
  • MARIADB_PASSWORD, pulled from your own environment

Restart policy

The restart policy here is unless-stopped, so Docker restarts MariaDB Galera after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Portainer puts these services on one shared private network, so they can find each other by name (like galera-1) while only the ports above are open to you.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set MariaDB Galera up. Add the template list to Portainer once, then deploying MariaDB Galera is a click rather than a wall of config.