pgAdmin
futomaki.pgadmin
A Docker Compose file for pgAdmin alone, generated from the catalog and checked by the safety inspector. No account needed.
Web-based administration and query tool for PostgreSQL, covering schema browsing, SQL editing, graphical query plans, session and lock monitoring, and role and permission management.
pgAdmin connects to one or more PostgreSQL servers and exposes their objects — databases, schemas, tables, functions, extensions — as a browsable tree with property and dependency views. The query tool runs ad-hoc SQL, renders explain plans graphically and exports result sets, while separate panels cover active sessions, locks and server statistics. Server definitions and preferences are stored per login account rather than globally. A first deployment sets the initial administrator email and password through the environment, then registers a connection to the PostgreSQL service on the same network.
You know it worked when
- The login page loads and accepts the configured administrator credentials.
- A PostgreSQL server registered by hostname connects successfully.
- The object browser lists the databases and schemas on that server.
- A query run in the query tool returns rows.
- Registered servers are still present after the container restarts.
Known sharp edges
- The initial administrator email and password come from environment variables and the container will not start without both.
- The configuration directory holds saved server definitions and any stored passwords and must be a persistent volume, or every connection has to be registered again.
- That mounted directory must be writable by the container's own user, and a permission mismatch fails at startup rather than at first use.
- It accumulates credentials for every registered database, so it should never be reachable publicly without authentication in front of it.