Self-host MariaDB with Adminer with Levelrail
A MariaDB 11.8 server paired with the Adminer web console, already wired together. The database is not published on the host, so other services in this project reach it at db:3306. Sign in to Adminer with server db, user root and the generated root password.
- Authorvrana
- LicenceApache-2.0
- Memory512 MiB
- Services2
How to self-host MariaDB with Adminer
-
Pull the images
2 images are pulled on your server.
Show images
adminer:5.5.1mariadb:11.8.9
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 8080.
-
Fill in the secrets
1 secret is generated and stored encrypted, 1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Open the page and sign in with system MySQL, server db, user root and the generated root password from the app secrets.
MariaDB with Adminer requirements
- Memory
- About 512 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then MariaDB with Adminer. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the MariaDB with Adminer docs page.
Deploy MariaDB with Adminer your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy MariaDB with Adminer from the CLI
levelrail-cli templates install mariadb-adminer --name my-mariadb-adminer Deploy MariaDB with Adminer with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/mariadb-adminer/install \
-d '{
"name": "my-mariadb-adminer"
}' MariaDB with Adminer configuration
MariaDB with Adminer services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| adminer | adminer:5.5.1 | 8080 | none |
| db | mariadb:11.8.9 | none | mariadb_data -> /var/lib/mysql |
MariaDB with Adminer environment variables
| Variable | Service | Value |
|---|---|---|
| ADMINER_DEFAULT_SERVER | adminer | Preset by the template |
| MARIADB_ROOT_PASSWORD | db | Generated at deploy |
Ports and volumes
- Ports
- 8080
- Volumes
- 1 named mount: mariadb_data -> /var/lib/mysql
MariaDB with Adminer FAQ
How much memory does MariaDB with Adminer need?
The catalog lists about 512 MiB of memory for MariaDB with Adminer across its 2 services.
Does MariaDB with Adminer run on arm64?
For MariaDB with Adminer, arm64 support is not confirmed; amd64 is unknown.
What licence is MariaDB with Adminer under?
MariaDB with Adminer is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does MariaDB with Adminer need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does MariaDB with Adminer bundle?
The template includes MySQL, running as its own service.
Which ports does MariaDB with Adminer use?
MariaDB with Adminer listens on port 8080 inside the stack.
Where does MariaDB with Adminer keep its data?
In a named volume: mariadb_data mounted at /var/lib/mysql.
Can I deploy MariaDB with Adminer on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for MariaDB with Adminer, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image adminer:5.5.1, mariadb:11.8.9 is what you deploy there.