Dockpeek

Self-hosted Docker container access, honestly reviewed. If you’ve ever stared at a sticky note trying to remember which port your Karakeep instance runs on, read on.

TL;DR

• What it is: A lightweight, MIT-licensed Docker dashboard focused on one job — show your containers, their ports, and let you click into them instantly [1][2].
• Who it’s for: Self-hosters, homelab operators, and developers who run many containers and want fast access without the overhead of Portainer or Docker Desktop [1][2].
• Cost savings: Free and open source. The only cost is a $5–10/mo VPS if you’re not already running one — but most users already are [README][4].
• Key strength: Zero configuration. You drop it in, point your browser at port 3420, and every container on your host is already listed with clickable port links [1][2].
• Key weakness: It is intentionally narrow in scope. No resource monitoring, no compose file management, no alerting. If you need those, Dockpeek won’t replace Portainer or Beszel [2][3].

---

What is Dockpeek

Dockpeek is a self-hosted Docker dashboard with a deliberately small surface area. It doesn’t try to be Portainer. It doesn’t try to be Docker Desktop. It solves exactly one problem: you have containers running, you can never remember what port they’re on, and you want to click into their web interfaces without typing docker ps every time.

The project is hosted at github.com/dockpeek/dockpeek and sits at 1,729 GitHub stars [merged profile]. It’s MIT-licensed, written in Python (Flask on the backend, Tailwind on the frontend), packaged as a Docker image, and ships ready to run with a four-line docker-compose file [README].

The XDA Developers review from September 2025 nails the core pitch in one paragraph: “Once up and running, Dockpeek automatically detects all your containers, lists the ports they expose, and turns them into clickable links. So, for example, if you’ve got Karakeep on port 3022, you no longer need to remember that. Just click the link, and you’ll be bounced straight into Karakeep with a one-click shortcut.” [1]

The second XDA review, from October 2025, frames it differently but lands in the same place: “It shows my containers, the ports I can access them from, if they’re running or not, and if they need an updated image.” [2] That sentence is essentially the full feature list, and the reviewer means it as a compliment.

---

Why people choose it

The people who choose Dockpeek are not people who wanted a lighter Portainer. They’re people who tried Portainer and found it overwhelming.

The October 2025 XDA review [2] is worth reading in full because the author explains the psychology clearly. He’s not anti-Portainer — he’s just done with tools that replicate information he already has elsewhere. He already has his compose files open in VS Code. He already knows where his storage folders are. He can monitor CPU from the OS. Every Docker management tool replicates that and then layers menus on top of it: “They all stack menus upon menus to show which containers are running, where your images are, and any little piece of information about your containers that the developer thinks you might want to see.” [2]

Dockpeek wins that comparison by not doing any of it. The dashboard shows containers, ports, run status, and update availability. Nothing else.

The September 2025 XDA review [1] makes the multi-host argument. If you split your containers across a NAS, a Raspberry Pi, and a main server, managing them in Portainer means either three separate Portainer instances or a Portainer Agent setup that requires its own configuration. Dockpeek handles it with environment variables in the compose file: add DOCKER_HOST_2_URL, DOCKER_HOST_3_URL, and all hosts appear on one dashboard [README][1].

The AlternativeTo page [4] shows the community perception: 8 likes, listed as an alternative to Dockhand, Licobox, Docker DB Manager, and Dockman. That’s a very specific orbit — all lightweight, UI-focused tools rather than full-blown container management platforms.

---

Features

From the README and first-hand reviews:

Core container visibility:

• Auto-detect all running containers with zero configuration [README][1][2]
• Display all published ports as clickable links [README][1]
• Detect HTTP vs. HTTPS automatically based on port conventions [1]
• Show container run status (running, stopped, unhealthy, paused) [README][4]
• Container counts by status (added in v1.6.5) [4]

Log access:

• Stream container logs in real time with a single click [README][2]
• Large, readable font in the log view — directly called out as a differentiator in the XDA review [2]

Image updates:

• Check all containers for newer image versions [README][1][2][4]
• Pull and upgrade outdated images from the dashboard [README]
• Image prune capability (added in v1.6.5) [4]
• Registry links for each image (added in v1.6.5) [4]

Multi-host support:

• Manage multiple Docker daemons from a single interface [README][1]
• Add hosts via environment variables — no UI configuration required [README]
• Each host appears as a named section; host name auto-detected from Docker API if not set [README]

Traefik integration:

• Automatically extract service URLs from Traefik container labels [README]
• No manual URL entry required if you’re already using Traefik as a reverse proxy [README]

Container labels:

• dockpeek.https — force HTTPS for specific ports [README]
• dockpeek.link — make container names clickable links [README]
• dockpeek.ports — add custom ports not auto-detected [README]
• dockpeek.port-range-grouping — control grouping of port ranges [README]
• dockpeek.tags — categorize containers with custom tags [README]

Docker Swarm support:

• Dedicated compose file for Swarm deployments [README]

What it explicitly does not do:

• No resource monitoring (CPU, memory, disk) — use Netdata or Beszel for that [3]
• No compose file management — use Dockge or Portainer for that [2][3]
• No alerting or uptime monitoring — use Uptime Kuma for that [3]
• No container creation or deployment from the UI

---

Pricing: SaaS vs self-hosted math

Dockpeek is free software under the MIT license. There is no SaaS tier, no cloud version, no paid plan, and no enterprise edition [merged profile][4]. The only cost is the infrastructure it runs on.

If you’re already running a homelab server or VPS for other containers, Dockpeek adds effectively zero cost — it’s another container on the same host.

If you’re starting from scratch, the infrastructure math looks like this:

Setup	Monthly cost
Dockpeek software	$0
Hetzner CX11 (2GB RAM VPS)	~$4–6/mo
Contabo VPS S	~$5–6/mo
Your own hardware (homelab)	Already paying

There’s no meaningful SaaS comparison here — there’s no commercial Docker dashboard product occupying the same niche that charges per seat or per container. The closest competitor in pricing terms is Portainer Business Edition, which charges per node and targets enterprises. Dockpeek targets neither of those use cases.

The honest note on pricing: Dockpeek has a Buy Me a Coffee link in the README, which signals a solo or small-team maintainer rather than a funded company [README]. That’s relevant context for anyone making a long-term infrastructure bet.

---

Deployment reality check

This is one of the easiest self-hosted tools to install. The basic docker-compose setup is four environment variables and one volume mount [README]:

services:
  dockpeek:
    image: dockpeek/dockpeek:latest
    container_name: dockpeek
    environment:
      - SECRET_KEY=your_secure_secret_key
      - USERNAME=admin
      - PASSWORD=admin
    ports:
      - "3420:8000"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    restart: unless-stopped

The XDA reviewer installed it through Portainer on a Synology NAS and described the process as: “outside of providing a secret key, changing the default username and password, there was no additional configuration needed.” [1] That matches the README’s claim of zero-config detection.

What you actually need:

• Any Linux host running Docker (including NAS devices, Raspberry Pi, VPS)
• Docker and docker-compose
• Port 3420 accessible in your browser (or a reverse proxy if you want a domain name)

Socket proxy setup (optional but recommended for security): Dockpeek requires access to the Docker socket, which has broad permissions by default. The README provides a dedicated docker-compose example using lscr.io/linuxserver/socket-proxy to limit API access to only the endpoints Dockpeek needs [README]. This is worth doing if you’re security-conscious, but adds about 10 minutes to setup.

Multi-host setup adds environment variables per host:

DOCKER_HOST_1_URL=unix:///var/run/docker.sock
DOCKER_HOST_2_URL=tcp://192.168.1.10:2375

The README includes a complete multi-socket compose example [README].

Time estimate: 10–15 minutes for a basic setup on a host you already control. 30 minutes if you’re adding a socket proxy and a reverse proxy for HTTPS. No database, no Redis, no SMTP required.

What can go sideways:

• The Docker socket mount gives Dockpeek broad access to your Docker daemon. Use the socket proxy pattern if you’re running this on a shared or semi-trusted host [README].
• Multi-host setups with remote sockets require those sockets to be exposed over TCP, which needs careful network security (firewall rules or VPN) [README].
• No authentication options beyond basic username/password — no SSO, no LDAP [merged profile]. Fine for personal use, not for team environments.

---

Pros and cons

Pros

• Zero configuration. Literally open the browser and your containers are there. The September 2025 XDA reviewer installed it via Portainer with no extra steps [1]. The October 2025 reviewer echoes this [2]. This isn’t marketing copy — it’s the actual experience.
• MIT licensed, no strings. Self-host it, fork it, embed it in your stack — no commercial agreement, no fair-code restrictions [merged profile][4].
• Multi-host in one view. Manage containers across multiple servers from a single dashboard without any Portainer Agent setup [README][1].
• One-click log access. The log view is specifically praised for being a single click away with a large, readable font — contrasted directly with Docker Desktop’s “even worse” logging section [2].
• Traefik integration works out of the box. If you’re already using Traefik labels, Dockpeek picks up service URLs automatically [README].
• Image update checking. Not a monitoring tool, but knowing a container is stale and being able to update it from the same dashboard is genuinely useful [1][2][4].
• Lightweight. Small Docker image, minimal dependencies, runs fine on a Raspberry Pi [1].
• Active development. v1.6.5 shipped container count displays, image prune, and registry links. 447 commits, updated through late 2025 [4][README].

Cons

• Intentionally minimal — not for everyone. If you want compose file management, Dockpeek is the wrong tool. The October 2025 reviewer chose it specifically because he was comfortable managing compose files in VS Code — that’s not most people [2].
• No resource monitoring. No CPU, memory, or disk graphs. Dockpeek doesn’t try to replace Netdata or Beszel [3]. If you want a single-pane monitoring view, you need both.
• No alerting. Dockpeek tells you what’s running right now, not what stopped at 3am. Pair it with Uptime Kuma for that [3].
• Basic authentication only. Username and password. No multi-user support, no SSO, no role-based access control [merged profile].
• Solo/small-team maintainer. The Buy Me a Coffee link and the project structure suggest this is not a company-backed product [README]. That’s not a disqualifier for homelab use, but it matters if you’re deploying this for a team that needs long-term support guarantees.
• No REST API or programmatic control. You can view containers from Dockpeek but you can’t drive it from scripts or other tools [merged profile].
• Docker socket security. The default setup mounts the full Docker socket, which is essentially root-equivalent access. The socket proxy workaround exists but is opt-in [README].

---

Who should use this / who shouldn’t

Use Dockpeek if:

• You run 10+ containers and spend time remembering port numbers.
• You’re already using Traefik and want automatic URL extraction from your existing labels.
• You manage containers across multiple hosts (NAS + server, or multiple VPSes) and want them in one view.
• You want a quick-access companion to heavier tools like Portainer — not a replacement.
• You’re comfortable managing compose files yourself and just want a visual access layer.

Skip it (use Portainer instead) if:

• You need to create, edit, or deploy containers from a UI.
• You want resource monitoring, volume management, or network inspection.
• Your team needs multi-user access or any form of access control.

Skip it (use Dockge instead) if:

• Your workflow centers on docker-compose stacks and you want a UI for managing those files.
• You want to see stack status, start/stop stacks, and edit compose YAML from the browser.

Skip it (use Beszel or Netdata instead) if:

• You need CPU, memory, and disk metrics. Dockpeek doesn’t touch system resources [3].

Use both Dockpeek and something else if:

• This is the most common pattern. The November 2025 XDA roundup lists Portainer, Beszel, Uptime Kuma, and Netdata as a homelab monitoring stack [3]. Dockpeek slots into that stack as the quick-access layer, not as a replacement for any of those tools.

---

Alternatives worth considering

• Portainer — the full-featured Docker management UI. Does everything Dockpeek does plus compose management, resource stats, multi-user access, and more. Business Edition has per-node pricing; Community Edition is free. Use Portainer when you need to manage containers, not just access them [2][3].
• Dockge — compose-file-first management. Built by the creator of Uptime Kuma. Strong at managing stacks; weaker at the quick-access use case Dockpeek owns [2][5].
• Arcane — listed on AlternativeTo as a popular alternative to Dockpeek. Docker management UI; less community data available at time of writing [4].
• Dockhand — listed as an alternative in the AlternativeTo community [4].
• Licobox — another community-suggested alternative for the lightweight dashboard category [4].
• Beszel — system monitoring (CPU, memory, disk) with container support. Different use case but frequently deployed alongside Dockpeek [3].
• Uptime Kuma — uptime monitoring and alerting. Complements Dockpeek rather than competes with it [3].

For the specific job of “show me my containers with clickable port links,” the realistic shortlist is Dockpeek vs Portainer Community Edition. Pick Dockpeek for minimal overhead and zero config. Pick Portainer when you need actual container management.

---

Bottom line

Dockpeek does one thing — gives you instant, clickable access to your container web interfaces — and it does it without asking anything in return. No database, no configuration, no learning curve. You drop it in, it detects your containers, and you never type docker ps | grep port again. For a homelab operator running a dozen services across one or two hosts, it’s the kind of tool you install once and forget about, which is the highest compliment you can pay a utility. The legitimate criticisms are that it’s intentionally narrow (no monitoring, no compose management, no alerting), relies on a solo maintainer rather than a funded company, and mounts the Docker socket with broad permissions unless you configure the socket proxy. None of that is a dealbreaker for personal use. For teams, the lack of multi-user support is a harder limit. But if you’ve ever had a sticky note on your NAS with port numbers written on it, you already know this is the tool you need.

---

Sources

1. Dhruv Bhutani, XDA Developers — “This zero-config self-hosted tool is a must install for all Docker enthusiasts” (Sep 2, 2025). https://www.xda-developers.com/zero-config-docker-self-hosted-ports/
2. Joe Rice-Jones, XDA Developers — “I replaced Docker Desktop with a new dashboard and I won’t go back” (Oct 18, 2025). https://www.xda-developers.com/hated-docker-until-found-this-dashboard-replacement/
3. Samir Makwana, XDA Developers — “These 8 Docker containers help monitor my entire home lab” (Nov 17, 2025). https://www.xda-developers.com/docker-containers-help-monitor-entire-home-lab/
4. AlternativeTo — “Dockpeek: Simple dashboard showing Docker ports with clickable links for multiple hosts”. https://alternativeto.net/software/dockpeek/about/
5. AlternativeTo — “Dockge: A fancy, easy-to-use and reactive self-hosted docker compose.”. https://alternativeto.net/software/dockge/about/

Primary sources:

• GitHub repository and README: https://github.com/dockpeek/dockpeek (1,729 stars, MIT license)