Connect Docker MySQL/PostgreSQL from HiDataLinker — free desktop GUI
Open a Docker Compose or docker-run MySQL or PostgreSQL database in HiDataLinker — free local-first desktop GUI via localhost port maps, no Adminer detour.
If your app stack is docker compose up and the database lives in a container, you should not need a browser Adminer tab every time you want to browse tables. HiDataLinker is a free, MIT-licensed, local-first desktop client for MySQL and PostgreSQL. Point it at the host port Docker published, and you get a light native GUI on the same machine as your containers.
Why a desktop GUI for Docker databases
- Compose already maps ports. Typical stacks expose
5432:5432or3306:3306(or a custom host port). Your PostgreSQL GUI for Docker / Docker MySQL desktop client just useslocalhostand that host port. - Same workflow as cloud URIs. When Compose also prints a
DATABASE_URL, you can paste it; otherwise fill host127.0.0.1, mapped port, user, password, and database name fromdocker-compose.yml. - Local-first fits local stacks. Credentials and connection profiles stay on your laptop — the same place the containers run.
What HiDataLinker adds
| Trait | What you get |
|---|---|
| Free open-source core | MIT — no seat, tab, or connection freemium wall for daily MySQL/PostgreSQL work |
| Local-first | Profiles and passwords stay on your machine |
| One desktop client | MySQL and PostgreSQL — one app for mixed Compose stacks |
| URL paste (optional) | Drop in a Compose DATABASE_URL when you have one |
| Light native UI | Tauri desktop — built to feel lighter than heavy Java clients |
Download: hidatalinker.onesolo.app · Source: github.com/henrybit/HiDataLinker
Practical path: localhost + published port
- Confirm the publish. In Compose, look for
ports:under thedb/postgres/mysqlservice (e.g."5432:5432"or"3307:3306"). The left number is what HiDataLinker uses on the host. - Start the stack.
docker compose up -d(or yourdocker run -p …equivalent) so the port is listening. - Connect from HiDataLinker. Host
127.0.0.1(orlocalhost), that host port, engine MySQL or PostgreSQL, plus user/password/database from the compose env. Or paste the matching connection URI if you keep one in.env. - Prefer host networking correctly. From the desktop on the host, use the published host port — not the container name (
db,postgres) and nothost.docker.internalunless another container is calling back to the host. Those names are for in-network / reverse cases, not for a GUI running on macOS/Windows/Linux outside the Compose network. - Optional Dump. Once connected, use HiDataLinker’s free Dump / same-engine migrate when you want a
.sqlsnapshot of the container DB onto another local connection.
Common gotchas
- Port already in use. If host Postgres/MySQL is already on 5432/3306, remap Compose (e.g.
5433:5432) and connect HiDataLinker to 5433. - Wrong auth plugin / empty password. Match
MYSQL_ROOT_PASSWORD/POSTGRES_PASSWORD(and user/db names) exactly; restart the service after env changes. - Health before click. Wait until the container is healthy; a “connection refused” usually means the publish is not up yet, not a broken GUI.
- No SSH-into-remote-Docker claim. This post is host → local published ports. Remote Docker hosts need your own tunnel or port forward first; then connect HiDataLinker to the forwarded localhost port.
Honest limits (v1)
v1 focuses on MySQL and PostgreSQL. HiDataLinker does not invent an in-app Docker context switcher or SSH-into-remote-daemon wizard — keep Compose (or a tunnel) providing a reachable TCP port, then connect. Linux builds may still be 敬请期待 depending on release; macOS Apple Silicon DMG is the documented download path on the site. No MCP or AI claims here.
Keywords this post owns: connect Docker Postgres GUI, Docker MySQL desktop client localhost, PostgreSQL GUI for Docker, docker compose database client, free MySQL PostgreSQL GUI.