dementev/adminer repository overview

⁠Adminer 6 — every database driver, native parallel dumps

Adminer 6 packaged with the drivers and client binaries it actually needs: MySQL, MariaDB, PostgreSQL, SQLite, MS SQL, Oracle, MongoDB, ClickHouse, Elasticsearch, Redis and SimpleDB, all from one image.

Dumps and restores shell out to the native clients instead of crawling through PHP row by row, and the worker pools size themselves to whatever CPU the container was given.

⁠Tags

Version tags are read out of the image after it is built and tested, so a tag can never claim an Adminer version the image does not contain.

mysql-nginx, mysql-standalone and mysql-fpm still resolve to the same digests. They're aliases now — the images stopped being MySQL-only — and they'll be dropped once nobody pulls them.

linux/amd64 only. SBOM, max-mode build provenance and a Cosign keyless signature on every published digest. Every merge to main publishes, plus a weekly rebuild for package updates.

⁠Quick start

docker run -d -p 127.0.0.1:8080:8080 dementev/adminer

services:
  adminer:
    image: dementev/adminer
    ports: ["127.0.0.1:8080:8080"]
    networks: [database]

⁠Databases

Firebird is the one Adminer driver missing: it needs ext-interbase, which doesn't exist for PHP 8.4.

The Oracle Instant Client is a sizeable chunk of the image. Building from source with --build-arg WITH_ORACLE=false drops it along with ext-oci8 and ext-pdo_oci.

⁠Faster dumps and restores

The export page grows extra output modes, all of which keep the data out of PHP's row-by-row loop:

• mysqldump → zstd and pg_dump → zstd — the native client piped straight into zstd -T0. An order of magnitude quicker than Adminer's own dump on a large database. Each one only appears on its own driver.
• gzip (pigz) and Zstandard (zstd CLI), on every driver — Adminer generates the dump, the CLI compressor uses all cores instead of PHP's single-threaded zlib.

Fast Restore in the sidebar takes an uploaded .sql, .sql.gz or .sql.zst and pipes it into mysql or psql. The PostgreSQL side runs in a single transaction with ON_ERROR_STOP, so a bad dump rolls back instead of leaving half a database behind.

The PostgreSQL client comes from PGDG rather than Debian's archive, because pg_dump 17 refuses to dump a PostgreSQL 18 server.

⁠Tuning

The entrypoint reads the container's CPU allowance — cgroup quota included, so --cpus=2 is respected rather than the host's core count — and sizes the worker pools from it. Everything it picks can be overridden:

⁠What's inside

• Debian trixie on php:8.4-fpm-trixie / php:8.4-cli-trixie.
• Adminer 6 (the full build), plugins for parallel dumps, fast restore and a dark-mode switcher.
• Client binaries: mysql, mysqldump, psql, pg_dump, sqlite3, zstd, pigz.
• Runs as www-data, dumb-init as PID 1, healthcheck on every flavor.
• server_tokens off, X-Robots-Tag on every response, open_basedir confined to what the app and the clients actually touch.
• nginx serves HTML, CSS and JS with gzip and brotli. The export content types are in neither filter's list, so a dump is never compressed twice or buffered on its way out.

⁠Security and provenance

Every published digest is built by the shared pipeline in vdementev/docker-workflows⁠. Pull requests build, test and scan without publishing; main is branch-protected, so nothing reaches Docker Hub without a green check behind it. A Trivy gate fails the build on any fixable CRITICAL or HIGH finding, and each published digest carries an SBOM, max-mode SLSA provenance and a keyless Cosign signature.

Verify what you pulled:

cosign verify \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  --certificate-identity-regexp 'github.com/vdementev/' \
  dementev/adminer:latest

SECURITY.md⁠ is the reporting channel and the response targets; SUPPORT.md⁠ covers tag lifecycle, pinning and patch cadence.

⁠Related images

One family, built by the same pipeline, meant to run together — a proxy in front, an app runtime, a database, and a way into it.

⁠Maintainer

Built and maintained by Vasilii Dementev⁠ at Lotus Web Agency⁠. These images are not a side project — they are the base layer under the client and product systems we run, which is why they are gated, tested and signed rather than pushed by hand.

Issues and pull requests: github.com/vdementev/adminer-docker⁠. Need this kind of infrastructure built or maintained for your own stack? lotuswebagency.com⁠.

Packaging, the bundled plugins and the configuration are MIT licensed — see LICENSE⁠. Adminer itself is vendored from adminer.org⁠ and keeps its own license (Apache 2.0 or GPL 2), as do the upstream driver plugins.