Skip to content
No description, website, or topics provided.
Dockerfile
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github update image link Oct 5, 2016
root #31 need to use backticks to support special characters in DB names Jul 8, 2019
.dockerignore transcode folder change, bump to 1.7, add ignore and templates Sep 17, 2016
.gitattributes transcode folder change, bump to 1.7, add ignore and templates Sep 17, 2016
.gitignore
Dockerfile
Dockerfile.aarch64 Switching to new Base images, shift to arm32v7 tag. Mar 24, 2019
Dockerfile.armhf Switching to new Base images, shift to arm32v7 tag. Mar 24, 2019
Jenkinsfile Bot Updating Templated Files Jun 8, 2019
LICENSE Bot Updating Templated Files May 25, 2019
README.md Bot Updating Templated Files Jul 6, 2019
jenkins-vars.yml
package_versions.txt Bot Updating Package Versions Aug 10, 2019
readme-vars.yml

README.md

linuxserver.io

The LinuxServer.io team brings you another container release featuring :-

  • regular and timely application updates
  • easy user mappings (PGID, PUID)
  • custom base image with s6 overlay
  • weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
  • regular security updates

Find us at:

  • Discord - realtime support / chat with the community and the team.
  • IRC - on freenode at #linuxserver.io. Our primary support channel is Discord.
  • Blog - all the things you can do with our containers including How-To guides, opinions and much more!

linuxserver/mariadb

Docker Pulls Docker Stars Build Status

Mariadb is one of the most popular database servers. Made by the original developers of MySQL.

mariadb

Supported Architectures

Our images support multiple architectures such as x86-64, arm64 and armhf. We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling linuxserver/mariadb should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

Architecture Tag
x86-64 amd64-latest
arm64 arm64v8-latest
armhf arm32v7-latest

Usage

Here are some example snippets to help you get started creating a container.

docker

docker create \
  --name=mariadb \
  -e PUID=1000 \
  -e PGID=1000 \
  -e MYSQL_ROOT_PASSWORD=<DATABASE PASSWORD> \
  -e TZ=Europe/London \
  -e MYSQL_DATABASE=<USER DB NAME> `#optional` \
  -e MYSQL_USER=<MYSQL USER> `#optional` \
  -e MYSQL_PASSWORD=<DATABASE PASSWORD> `#optional` \
  -p 3306:3306 \
  -v <path to data>:/config \
  --restart unless-stopped \
  linuxserver/mariadb

docker-compose

Compatible with docker-compose v2 schemas.

---
version: "2"
services:
  mariadb:
    image: linuxserver/mariadb
    container_name: mariadb
    environment:
      - PUID=1000
      - PGID=1000
      - MYSQL_ROOT_PASSWORD=<DATABASE PASSWORD>
      - TZ=Europe/London
      - MYSQL_DATABASE=<USER DB NAME> #optional
      - MYSQL_USER=<MYSQL USER> #optional
      - MYSQL_PASSWORD=<DATABASE PASSWORD> #optional
    volumes:
      - <path to data>:/config
    ports:
      - 3306:3306
    restart: unless-stopped

Parameters

Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

Parameter Function
-p 3306 Mariadb listens on this port.
-e PUID=1000 for UserID - see below for explanation
-e PGID=1000 for GroupID - see below for explanation
-e MYSQL_ROOT_PASSWORD=<DATABASE PASSWORD> Set this to root password for installation (minimum 4 characters).
-e TZ=Europe/London Specify a timezone to use EG Europe/London.
-e MYSQL_DATABASE=<USER DB NAME> Specify the name of a database to be created on image startup.
-e MYSQL_USER=<MYSQL USER> This user will have superuser access to the database specified by MYSQL_DATABASE.
-e MYSQL_PASSWORD=<DATABASE PASSWORD> Set this to the password you want to use for you MYSQL_USER (minimum 4 characters).
-v /config Contains the db itself and all assorted settings.

User / Group Identifiers

When using volumes (-v flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1000 and PGID=1000, to find yours use id user as below:

  $ id username
    uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)

 

Application Setup

If you didn't set a password during installation, (see logs for warning) use mysqladmin -u root password <PASSWORD> to set one at the docker prompt...

NOTE changing the MYSQL_ROOT_PASSWORD variable after the container has set up the initial databases has no effect, use the mysqladmin tool to change your mariadb password.

NOTE if you want to use (MYSQL_DATABASE MYSQL_USER MYSQL_PASSWORD) all three of these variables need to be set you cannot pick and choose.

Unraid users, it is advisable to edit the template/webui after setup and remove reference to this variable.

Find custom.cnf in /config for config changes (restart container for them to take effect) , the databases in /config/databases and the log in /config/log/myqsl

Support Info

  • Shell access whilst the container is running: docker exec -it mariadb /bin/bash
  • To monitor the logs of the container in realtime: docker logs -f mariadb
  • container version number
    • docker inspect -f '{{ index .Config.Labels "build_version" }}' mariadb
  • image version number
    • docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/mariadb

Updating Info

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.

Below are the instructions for updating containers:

Via Docker Run/Create

  • Update the image: docker pull linuxserver/mariadb
  • Stop the running container: docker stop mariadb
  • Delete the container: docker rm mariadb
  • Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
  • Start the new container: docker start mariadb
  • You can also remove the old dangling images: docker image prune

Via Docker Compose

  • Update all images: docker-compose pull
    • or update a single image: docker-compose pull mariadb
  • Let compose update all containers as necessary: docker-compose up -d
    • or update a single container: docker-compose up -d mariadb
  • You can also remove the old dangling images: docker image prune

Via Watchtower auto-updater (especially useful if you don't remember the original parameters)

  • Pull the latest image at its tag and replace it with the same env variables in one run:
    docker run --rm \
    -v /var/run/docker.sock:/var/run/docker.sock \
    containrrr/watchtower \
    --run-once mariadb
    

Note: We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.

  • You can also remove the old dangling images: docker image prune

Building locally

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone https://github.com/linuxserver/docker-mariadb.git
cd docker-mariadb
docker build \
  --no-cache \
  --pull \
  -t linuxserver/mariadb:latest .

The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static

docker run --rm --privileged multiarch/qemu-user-static:register --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

Versions

  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
  • 07.03.19: - Add ability to setup a database and default user on first spinup.
  • 26.01.19: - Add pipeline logic and multi arch.
  • 10.09.18: - Rebase to ubuntu bionic and use 10.3 mariadb repository.
  • 09.12.17: - Fix continuation lines.
  • 12.09.17: - Gracefully shut down mariadb.
  • 27.10.16: - Implement linting suggestions on database init script.
  • 11.10.16: - Rebase to ubuntu xenial, add version labelling.
  • 09.03.16: - Update to mariadb 10.1. Change to use custom.cnf over my.cnf in /config. Restructured init files to change config options on startup, rather than in the dockerfile.
  • 26.01.16: - Change user of mysqld_safe script to abc, better unclean shutdown handling on restart.
  • 23.12.15: - Remove autoupdating, between some version updates the container breaks.
  • 12.08.15: - Initial Release.
You can’t perform that action at this time.