Mini DBA containers for Linux
Run Mini DBA Engine and Mini DBA Console using the supported Docker Compose bundle on a 64-bit Linux host.
The bundle includes persistent storage, same-host deployment, and separate-VM deployments. The Console is published on port 8080; put it behind HTTPS before exposing it outside a trusted network.
Linux container deployment
Mini DBA has separate Linux container images for the monitoring Engine and browser Console. Native Linux packages are not part of the supported public release.
| Image | Purpose | Default port |
|---|---|---|
ghcr.io/minidba/minidba-engine |
Runs Mini DBA Engine and monitors database servers. | 8734 Engine service |
ghcr.io/minidba/minidba-console |
Runs the browser Console and its hosted MCP endpoint. | 8080 HTTP |
The downloadable Compose bundle supports same-host and split-VM deployments while keeping operational data outside the container images. For complete command-by-command guidance, see Install the Mini DBA Engine container on Linux and Install the Mini DBA Console container on Linux.
Same-host installation
If unsure if you need same or different host, install both containers on same host.
Extract the bundle and run:
bash install.sh /data/minidbaOpen http://VM-NAME-OR-IP:8080. In Console Settings, connect to net.tcp://engine:8734/MiniDBAService/tcp.
Engine and Console on separate VMs
The same bundle includes supported split-vm/engine and split-vm/console Compose deployments. Install Engine on a VM close to the monitored databases, install Console on a separate web-facing VM, and connect them over a private network.
# Engine VM
cd split-vm/engine
bash install.sh 10.0.1.10 /var/lib/minidba-engine
# Console VM
cd split-vm/console
bash install.sh /var/lib/minidba-consoleAllow TCP 8734 from the Console VM to the Engine VM only, then add net.tcp://engine-vm.private.example:8734/MiniDBAService/tcp in Console Settings. Publish Console through HTTPS; never expose Engine port 8734 directly to the internet.
Persistent data and upgrades
Keep the Engine and Console data directories on persistent storage and back them up before upgrades. Use the bundle's manage.sh upgrade command to pull the configured image versions and replace the containers without deleting persistent data.