The architectures supported by this image are:
| Architecture | repo |
|---|---|
| x86-64 | betothreeprod/mariadb-intel-nuc |
| arm64 | betothreeprod/mariadb-raspberrypi3-64 |
| armhf | betothreeprod/mariadb-raspberrypi3 |
Here are some example snippets to help you get started creating a container.
docker create \
--name=mariadb \
-e PUID=1000 \
-e PGID=1000 \
-e MYSQL_ROOT_PASSWORD=ROOT_ACCESS_PASSWORD \
-e TZ=Europe/London \
-e MYSQL_DATABASE=USER_DB_NAME `#optional` \
-e MYSQL_USER=MYSQL_USER `#optional` \
-e MYSQL_PASSWORD=DATABASE_PASSWORD `#optional` \
-e REMOTE_SQL=http://URL1/your.sql,https://URL2/your.sql `#optional` \
-p 3306:3306 \
-v path_to_data:/config \
--restart unless-stopped \
linuxserver/mariadb
Compatible with docker-compose v2 schemas.
---
version: "2.1"
services:
mariadb:
image: betothreeprod/mariadb-%%BALENA_MACHINE_NAME%%
container_name: mariadb
environment:
- PUID=1000
- PGID=1000
- MYSQL_ROOT_PASSWORD=ROOT_ACCESS_PASSWORD
- TZ=Europe/London
- MYSQL_DATABASE=USER_DB_NAME #optional
- MYSQL_USER=MYSQL_USER #optional
- MYSQL_PASSWORD=DATABASE_PASSWORD #optional
- REMOTE_SQL=http://URL1/your.sql,https://URL2/your.sql #optional
volumes:
- path_to_data:/config
ports:
- 3306:3306
restart: unless-stopped
%%BALENA_MACHINE_NAME%% it's the template variable for the host system name from Balena OS reference.
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 $USER
uid=1000(thedockeruser) gid=1000(thedockergroup) groups=1000(thedockergroup)
Content type
Image
Digest
Size
137.2 MB
Last updated
over 6 years ago
docker pull betothreeprod/mariadb-raspberrypi3